rsc-universal 0.1.1

package/skills/linkedin-content/scripts/verify.sh

@@ -0,0 +1,154 @@
+#!/usr/bin/env bash
+#
+# verify.sh — mechanical reach-killer lint for a drafted LinkedIn post.
+#
+# WHAT IT DOES (read-only; never edits or writes a file)
+#   Static, network-free checks over ONE draft post file (.txt / .md) you point
+#   it at. It catches the four mechanical things that throttle reach — NOT
+#   judgment (whether the hook pulls or the CTA is answerable lives in the eval):
+#     1. Hook length: the first text block (up to the first blank line) is over
+#        ~210 chars -> warn (the mobile feed truncates ~150–210 chars before
+#        'see more'; an over-long hook line either truncates mid-clause or buries
+#        the payoff-seed).
+#     2. Body link: any http:// or https:// in the draft -> FAIL (a body link
+#        costs ~60% of reach; the 'link in first comment' workaround is also
+#        penalized as of early 2026 — put the URL nowhere).
+#     3. Dead CTA: a banned low-effort CTA ('thoughts?', 'agree?',
+#        'let me know below', 'what do you think?', 'drop a comment') -> warn
+#        (these get a like, not a comment; comments weigh ~15x).
+#     4. Wall of text: a paragraph block with > 3 sentence-enders (. ! ?) and no
+#        blank-line break inside it -> warn (walls tank dwell ~40% vs. broken copy).
+#
+#   Only #2 is a hard failure. Everything else is a warning. A clean OR empty/
+#   missing-content file exits 0 — never a false failure.
+#
+# HOW TO RUN (inside YOUR project, not the skills repo)
+#   ./verify.sh draft.md                 # warnings + the hard link check
+#   ./verify.sh draft.md --hook 150      # tighten the hook char ceiling
+#   ./verify.sh draft.md --strict        # treat warnings as failures (CI gate)
+#
+# EXIT CODES
+#   0  clean, warnings only (without --strict), or empty/missing-content file
+#   1  a hard failure (a body link) — or any warning under --strict
+#   2  bad usage (no file given, or file does not exist)
+#
+# Runs on stock macOS bash 3.2: no mapfile, no associative arrays, no bc.
+
+set -euo pipefail
+
+if [ -t 1 ]; then
+  RED=$'\033[31m'; GREEN=$'\033[32m'; YELLOW=$'\033[33m'; NC=$'\033[0m'
+else
+  RED=''; GREEN=''; YELLOW=''; NC=''
+fi
+
+warn_count=0; fail_count=0
+ok()   { printf '%s[ ok ]%s %s\n' "$GREEN"  "$NC" "$*"; }
+warn() { printf '%s[warn]%s %s\n' "$YELLOW" "$NC" "$*"; warn_count=$((warn_count + 1)); }
+fail() { printf '%s[fail]%s %s\n' "$RED"    "$NC" "$*"; fail_count=$((fail_count + 1)); }
+
+usage() { sed -n '2,35p' "$0" | sed 's/^# \{0,1\}//'; }
+
+FILE=""
+HOOK_MAX=210
+STRICT=0
+while [ $# -gt 0 ]; do
+  case "$1" in
+    -h|--help) usage; exit 0 ;;
+    --hook) HOOK_MAX="${2:-210}"; shift 2 ;;
+    --strict) STRICT=1; shift ;;
+    -*) printf '%sunknown option: %s%s\n' "$RED" "$1" "$NC" >&2; usage; exit 2 ;;
+    *) if [ -z "$FILE" ]; then FILE="$1"; fi; shift ;;
+  esac
+done
+
+if [ -z "$FILE" ]; then
+  printf '%sno draft file given%s\n' "$RED" "$NC" >&2; usage; exit 2
+fi
+if [ ! -f "$FILE" ]; then
+  printf '%sfile not found: %s%s\n' "$RED" "$FILE" "$NC" >&2; exit 2
+fi
+
+# Empty / whitespace-only file: nothing to check, do not false-fail.
+if [ ! -s "$FILE" ] || ! grep -q '[^[:space:]]' "$FILE" 2>/dev/null; then
+  ok "empty file — nothing to check"
+  exit 0
+fi
+
+printf 'linkedin-content verify — %s (hook ceiling=%s chars)\n\n' "$FILE" "$HOOK_MAX"
+
+# --- 1. hook length (first non-empty block up to the first blank line) --------
+# Skip a leading YAML/front-matter fence if present, then take the first block.
+HOOK_BLOCK="$(awk '
+  BEGIN { infm=0; started=0; done=0 }
+  NR==1 && $0 ~ /^---[[:space:]]*$/ { infm=1; next }
+  infm==1 && $0 ~ /^---[[:space:]]*$/ { infm=0; next }
+  infm==1 { next }
+  done==1 { next }
+  /^[[:space:]]*$/ { if (started==1) { done=1 }; next }
+  { started=1; print }
+' "$FILE")"
+HOOK_LEN="$(printf '%s' "$HOOK_BLOCK" | tr -d '\n' | wc -m | tr -d '[:space:]')"
+HOOK_LEN="${HOOK_LEN:-0}"
+if [ "$HOOK_LEN" -gt "$HOOK_MAX" ]; then
+  warn "hook block is ~${HOOK_LEN} chars (over the ${HOOK_MAX}-char ceiling) — it truncates or buries the payoff before 'see more'"
+else
+  ok "hook block ~${HOOK_LEN} chars (<= ${HOOK_MAX})"
+fi
+
+# --- 2. body link (hard) ------------------------------------------------------
+if grep -Eiq 'https?://' "$FILE"; then
+  LINKS="$(grep -Eio 'https?://[^[:space:]]+' "$FILE" | sort -u | head -3 | tr '\n' ' ')"
+  fail "link in body: ${LINKS}— a body link costs ~60% reach and 'link in first comment' is now penalized too; remove it"
+else
+  ok "no http(s) link in body"
+fi
+
+# --- 3. dead CTAs -------------------------------------------------------------
+DEAD='thoughts\?|agree\?|let me know below|what do you think\?|drop a comment'
+HITS="$(grep -Eio "$DEAD" "$FILE" 2>/dev/null | sort -u || true)"
+if [ -n "$HITS" ]; then
+  while IFS= read -r h; do
+    [ -n "$h" ] && warn "dead CTA present: \"$h\" — ask what only the reader can answer (comments weigh ~15x likes)"
+  done <<EOF
+$HITS
+EOF
+else
+  ok "no dead CTAs"
+fi
+
+# --- 4. wall of text (a block with >3 sentence-enders and no inner break) -----
+WALLS="$(awk '
+  BEGIN { RS=""; n=0 }
+  {
+    # count sentence-enders in this blank-line-delimited block
+    s = gsub(/[.!?]+/, "&")
+    if (s > 3) { n++; print "block " n " has " s " sentences with no line break" }
+  }
+' "$FILE")"
+if [ -n "$WALLS" ]; then
+  while IFS= read -r w; do
+    [ -n "$w" ] && warn "wall of text: $w — split into 1–2 sentence paragraphs (walls cut dwell ~40%)"
+  done <<EOF
+$WALLS
+EOF
+else
+  ok "no wall-of-text blocks"
+fi
+
+# --- summary ------------------------------------------------------------------
+printf '\n'
+if [ "$fail_count" -gt 0 ]; then
+  printf '%s%d hard failure(s), %d warning(s)%s\n' "$RED" "$fail_count" "$warn_count" "$NC"
+  exit 1
+fi
+if [ "$warn_count" -gt 0 ]; then
+  if [ "$STRICT" -eq 1 ]; then
+    printf '%s%d warning(s) — failing under --strict%s\n' "$YELLOW" "$warn_count" "$NC"
+    exit 1
+  fi
+  printf '%s%d warning(s), 0 hard failures%s\n' "$YELLOW" "$warn_count" "$NC"
+  exit 0
+fi
+printf '%sall checks passed%s\n' "$GREEN" "$NC"
+exit 0

package/skills/linkedin-outreach/SKILL.md

@@ -0,0 +1,174 @@
+---
+name: linkedin-outreach
+description: "Use when running LinkedIn-native social selling as a repeatable motion: building Sales Navigator saved searches and trigger alerts, fixing a low connection-acceptance rate, designing a daily social-selling routine, turning profile views / post engagers / accepted connections into warm conversations, and logging every touch so the loop is measurable. Triggers: 'set up a Sales Nav saved search and alert me on job changes', 'how many connection requests per week without getting flagged', 'my acceptance rate is in the toilet', 'someone viewed my profile, what is the play', 'turn the people who liked my post into conversations', 'munta'm una rutina de social selling a LinkedIn', '¿cuántas invitaciones puedo enviar por semana'. This owns the loop and its ledger, NOT writing the cold connection note or DM copy (that is cold-outreach)."
+tags: [linkedin, social-selling, sales-navigator, outreach, pipeline]
+recommends: [cold-outreach, lead-gen, sales-pipeline, linkedin-strategy, linkedin-content]
+origin: risco
+---
+
+# Linkedin Outreach — The Loop and Its Ledger
+
+*You run the LinkedIn social-selling motion and keep its score. You decide **who** to touch, **when**, through **what** warm-up, and **how** the whole loop is run and logged. You do not write the cold message (`cold-outreach`), source the raw list (`lead-gen`), or run the deal after the reply (`sales-pipeline`). The thesis is warm-first: engagement before connection, signal before send, ledger before "I'll remember it."*
+
+This skill is a *motion*, not a message. Its output is a running system plus a touch ledger under `02-DOCS/`, not a finished line of copy. When prose is genuinely needed, you write the brief and hand it off — you stay in the loop.
+
+## When to use
+
+- "Set up a Sales Navigator saved search / lead list for [ICP] and the trigger alerts."
+- "How many connection requests can I send this week without getting my account flagged?"
+- "Build me a 30-min-a-day social-selling routine that turns LinkedIn into pipeline."
+- "My acceptance rate is ~15% — how do I run requests so people actually accept?"
+- "Turn everyone who engaged with my last post into a conversation."
+- "Someone viewed my profile / liked my post — what's the play?"
+- "Log my LinkedIn touches and show me what's converting."
+- "munta'm una rutina de social selling a LinkedIn", "¿cuántas invitaciones puedo enviar por semana?"
+
+## When NOT — the boundary that gets fought over
+
+The sharpest line is against **cold-outreach**. Hold it:
+
+- **A single message** — the connection note (≤300 chars), the DM bump, its wording and per-inbox send cadence → `../cold-outreach/SKILL.md`. If the ask is "write this" or "fix this template," it is not yours.
+- **The system** — who to touch, when, the warm-up, the budget, the ledger → here. When both are in play, **this skill drives and delegates the copy.**
+
+Other routes:
+
+- Sourcing / scoring the raw prospect list, ICP definition, dedupe → `../lead-gen/SKILL.md`.
+- Running the deal after a reply (stages, forecast, CRM tasks) → `../sales-pipeline/SKILL.md`.
+- Writing/scheduling LinkedIn *posts* → `../linkedin-content/SKILL.md`.
+- Brand growth/positioning strategy → `../linkedin-strategy/SKILL.md`.
+
+## The loop
+
+Five phases, in order. Each has a *why* and yields one artifact; the artifact gates the next phase. Skipping a phase is how acceptance collapses.
+
+1. **Target** — *why:* outreach timed to a reason beats outreach timed to a calendar. → Yields a Sales Nav saved search + trigger alerts (job change, funding, recent post).
+2. **Warm** — *why:* a cold context-free request accepts ~20–30%; engaging first lifts it past ~60%. → Yields a logged pre-touch (profile view + one genuine comment/like 1–2 days prior).
+3. **Connect** — *why:* the request is the smallest, most rate-limited move; spend it deliberately. → Yields a sent request inside the weekly budget, note-or-no-note chosen by goal.
+4. **Convert** — *why:* an accept is not a conversation; the choreography turns a signal into a warm 1:1. → Yields a thread with a real reply, copy delegated to cold-outreach when needed.
+5. **Log** — *why:* a motion you can't measure you can't repeat or fix. → Yields a row in the `02-DOCS/` ledger with the outcome.
+
+Each phase has its own section below. Run them as a daily checklist (last section).
+
+## Target with Sales Navigator
+
+Build the saved search from the ICP, not from a name list:
+
+- **Filters that matter:** geography, current job title (use the title field, not keywords, to avoid past-role noise), seniority, company headcount, industry, and `Posted on LinkedIn in past 30 days` (active profiles accept and reply far more). Save it; Sales Nav re-runs it and surfaces new matches.
+- **Trigger alerts worth turning on:** *changed jobs in last 90 days* (new role = new budget, new pain), *company funding events*, and *posted recently* (a fresh post is your warm-up hook). Time the request to a trigger, never to a Tuesday.
+- **InMail reality:** Core and Advanced both ship **50 InMail credits/mo**, rolling over up to 3 months (max 150 accumulated); an InMail that gets a reply within 90 days is **credited back**. Spend InMail on out-of-network leads where a connection request can't reach — not on people you could warm up and connect to for free.
+
+Free vs Core vs Advanced — buy on the job, not the brand:
+
+| You need | Tier | 2025 price | Why |
+| --- | --- | --- | --- |
+| Run the loop on a tight ICP, manual budget | Free | $0 | Works if you stay disciplined; no saved-search alerts. |
+| Saved searches, 40+ filters, lead/account alerts, 50 InMail/mo | Core | $119.99/mo ($1,079.88/yr) | The default for a working social seller. |
+| + TeamLink, Smart Links, buyer-intent, Account/Lead IQ, CRM sync | Advanced | $159.99/mo ($1,799.88/yr) | Only when a team or CRM sync is real. |
+
+Filter recipes per ICP, trigger-alert setup, and the full Core-vs-Advanced buy math → `references/sales-navigator-playbook.md`.
+
+## The connection motion
+
+**Engagement-before-connect ritual.** 1–2 days before the request: view the profile, follow the company page, and drop **one genuine** comment or like on a recent post. This is what moves acceptance from ~20–30% (cold) to ~60%+. Log the pre-touch — it is phase 2, not optional flavor.
+
+**Note or no note — read the paradox correctly.** A personalized note barely moves *acceptance* (26.42% with vs 26.37% without; some 2025/26 datasets show no-note accepting *higher*). But a note with real context nearly **doubles the post-accept reply rate** (9.36% vs 5.44%). So decide by goal:
+
+| Your goal | Note? | Why |
+| --- | --- | --- |
+| Maximize the **accept** (build network, retarget later) | No note (or near-empty) | Notes don't lift acceptance; an empty request often accepts as well or better. |
+| Maximize the **reply** after accept | Short context note | Real context roughly doubles reply; worth the friction only when you have a true hook. |
+| No genuine hook exists | No note | A generic note is worse than none — it reads as a pitch. |
+
+When you do send a note, you do **not** write it here — hand the brief (the hook, the person, the goal) to `../cold-outreach/SKILL.md`.
+
+**Weekly request budget — the cap is a rolling weekly limit, not a daily reset.**
+
+| Account | Realistic weekly cap | Daily target | Health rule |
+| --- | --- | --- | --- |
+| Free | ~100/wk | ~20/weekday, stay under ~80/wk | Pause and warm more if acceptance drops below ~30%. |
+| Premium / Sales Nav | up to ~200/wk | up to ~40/day | Only with strong SSI and acceptance >40%; otherwise treat as free. |
+
+Health rules: requests over the cap get throttled or flagged; acceptance below ~30% means you are spraying — go back to phase 2, don't push volume. Withdraw stale pending requests before they pile up.
+
+## Engagement → conversation
+
+A signal is an opening. Match the signal to a play; the play is choreography (timing, sequence, what to reference), never finished prose.
+
+| Signal | Play | Copy? |
+| --- | --- | --- |
+| Connection just accepted | Wait, don't pitch. Reference *why* you reached out (their post/role/trigger), ask one genuine question. | Brief → cold-outreach |
+| Profile viewer (they viewed you) | Soft, warm reply: "Saw you stopped by — noticed [their thing], curious how you handle X?" | Brief → cold-outreach |
+| Post engager (liked/commented your post) | Thank or build on their comment, then DM a related question tied to their work. | Brief → cold-outreach |
+| Comment thread (they engaged a third party's post) | Add value in-thread first, connect with that context the next day. | Brief → cold-outreach |
+
+Worked example — the move, not the words:
+
+```text
+Bad  (pitch-on-accept):
+  Accepted → "Thanks for connecting! We help teams like yours cut reporting
+  time 40% with our analytics platform — open to a 15-min demo Thursday?"
+  Reads as a trap; reply rate craters.
+
+Good (reference-then-ask):
+  Accepted → "Appreciate the connect — your post on attribution gaps in
+  ecommerce hit home. How are you splitting paid vs organic credit right now?"
+  Opens a real thread; the product never comes up until they ask.
+```
+
+## Hand off to pipeline
+
+You run the loop up to a **warm intro or a booked call** — then you stop and hand off.
+
+Buying-signal tells in a thread: they ask about price/timeline, mention an active project or pain, reference budget or a decision date, or say "send me more." When you see one:
+
+1. Book the call or send the warm intro.
+2. Log the outcome (`call_booked`) in the ledger.
+3. Hand the thread + context to `../sales-pipeline/SKILL.md`.
+
+**Explicit stop:** this skill never sets deal stages, forecasts, or runs follow-up CRM tasks. The moment a deal exists, it is sales-pipeline's.
+
+## The ledger (02-DOCS)
+
+One file. Path: `02-DOCS/linkedin-outreach/touches.csv`. The header row is fixed (verify.sh checks it verbatim):
+
+```csv
+date,name,profile_url,channel,trigger,action,stage,outcome,next_touch
+```
+
+- `channel`: `connect` | `inmail` | `dm` | `comment` | `view`.
+- `outcome` (enum, no blanks): `requested` | `accepted` | `replied` | `conversation` | `call_booked` | `dead`.
+- Never leave a literal merge token (`{first_name}`, `[company]`, `XXXX`, `TODO`) in a cell — verify.sh fails on it.
+
+Full column spec, the outcome enum, a filled 5-row example, and the weekly-review formulas → `references/ledger-schema.md`.
+
+**Weekly review ritual** (15 min, same day each week). Compute from the ledger:
+
+- **Acceptance %** = accepted ÷ requested.
+- **Post-accept reply %** = replied ÷ accepted.
+- **Conversations → calls %** = call_booked ÷ conversation.
+- **Touches/week** = rows added this week (is the loop actually running?).
+
+If acceptance < ~30%, warm harder (phase 2). If reply < ~10%, your hooks are weak (better brief to cold-outreach). If touches/week is near zero, the loop stopped — that's the real failure.
+
+## Anti-patterns
+
+| Bad | Why it bites | Do instead |
+| --- | --- | --- |
+| Spray connection requests over the cap | Rolling weekly limit; throttled or account-flagged | Stay under ~80/wk free, ~200 Premium with >40% accept |
+| Pitch the instant a connection accepts | Reads as a trap; reply rate craters | Reference their context, ask one real question first |
+| Automation that ignores the rolling limit | Bursts trip LinkedIn's detection; account at risk | Pace within the budget; warm-up beats volume |
+| Read "notes don't help" as "context never helps" | Notes don't lift *accept*, but context doubles *reply* | Decide note by goal: accept→none, reply→context |
+| Chase SSI as the goal | SSI is a lagging proxy; high SSI ≠ pipeline | Track acceptance/reply/calls; let SSI follow |
+| Run outreach with no ledger | No measurement → no repeatable motion | Log every touch + outcome to `02-DOCS/` |
+
+## Daily 30-minute routine
+
+Run this as a checklist; it is the loop compressed into a day.
+
+- [ ] **Engage (10 min):** comment genuinely on 5–8 posts from your saved search and from people you plan to connect with this week (phase 2 warm-up bank).
+- [ ] **Connect (5 min):** send today's requests from the saved search / trigger alerts, inside the weekly budget; note-or-no-note by goal (phase 3).
+- [ ] **Convert (10 min):** progress 2–3 warm threads — accepted connections, profile viewers, post engagers — using the signal→play table; delegate any copy to cold-outreach.
+- [ ] **Hand off (2 min):** any buying signal → book/intro, then route to sales-pipeline.
+- [ ] **Log (3 min):** write every touch and outcome to `02-DOCS/linkedin-outreach/touches.csv`.
+
+Weekly, run the review ritual and adjust the next week's targeting. That closes the loop back to phase 1.

package/skills/linkedin-outreach/evals/README.md

@@ -0,0 +1,3 @@
+# Evals — linkedin-outreach
+
+These cases are read by the catalog's routing harness (or by hand); there is no bundled runner. `should_trigger` asserts the SKILL.md description + body are specific enough that the listed prompt loads `linkedin-outreach`. `should_not_trigger` asserts a near-miss prompt routes to the named real sibling instead (each `route_to` id — `cold-outreach`, `lead-gen`, `sales-pipeline`, `linkedin-content`, `linkedin-strategy` — exists in the catalog). `capability` is a rubric: feed the scenario to an agent with this skill loaded and grade the generated motion against every `must_include` bullet (each is pass/fail). To sanity-check a *generated ledger* against the schema and placeholder banlist, run `../scripts/verify.sh path/to/touches.csv` from this directory — it is read-only, defaults to `02-DOCS/linkedin-outreach/touches.csv`, and exits 0 cleanly when no ledger exists yet.

package/skills/linkedin-outreach/evals/cases.yaml

@@ -0,0 +1,43 @@
+skill: linkedin-outreach
+
+should_trigger:
+  - prompt: "Set up a Sales Navigator saved search for Series-B fintech RevOps leaders and alert me on job changes."
+    why: Core targeting phase — saved search + trigger alerts, the spine of the loop.
+  - prompt: "My LinkedIn acceptance rate is about 15%. How do I run my connection requests so people actually accept?"
+    why: Non-obvious — names a metric, not the skill; routes to engagement-before-connect + the weekly budget rules.
+  - prompt: "Build me a 30-minute-a-day social-selling routine that turns LinkedIn into pipeline."
+    why: The loop plus the daily checklist — the motion, not any message.
+  - prompt: "Turn everyone who engaged with my last post into a conversation, and log who I've touched."
+    why: Engagement-to-conversation play plus the 02-DOCS ledger.
+  - prompt: "Someone just viewed my profile and another person liked my post — what's the play?"
+    why: Non-obvious signal-to-play question; the choreography, never the finished copy.
+  - prompt: "Munta'm una rutina de social selling a LinkedIn i porta'm un registre dels contactes."
+    why: Catalan — the loop plus the ledger.
+
+should_not_trigger:
+  - prompt: "Write the actual connection note and the DM bump for these 5 prospects."
+    route_to: cold-outreach
+    why: The message copy and its send cadence, not the motion — the sharpest near-miss.
+  - prompt: "Find me 200 SaaS CTOs with verified profiles to target."
+    route_to: lead-gen
+    why: Sourcing and scoring the raw prospect list.
+  - prompt: "A prospect replied 'interested' — set the deal stage and my follow-up tasks."
+    route_to: sales-pipeline
+    why: Running the deal after the reply.
+  - prompt: "Write and schedule my next 4 LinkedIn posts."
+    route_to: linkedin-content
+    why: Publishing content, not 1:1 outreach.
+  - prompt: "Define my overall LinkedIn positioning and growth strategy for the year."
+    route_to: linkedin-strategy
+    why: Brand growth/positioning, not the outreach loop.
+
+capability:
+  - scenario: "I sell a $20k analytics tool to ecommerce ops leads. Set up my LinkedIn social-selling motion end to end."
+    must_include:
+      - Defines a Sales Navigator saved search with concrete filters plus trigger alerts (job change / funding / recent post).
+      - Specifies the engagement-before-connect ritual (view + one genuine comment/like 1–2 days prior) and the acceptance lift it buys.
+      - Gives a note-or-no-note decision tied to the acceptance-vs-reply goal (the note paradox).
+      - States the weekly connection-request budget and at least one health rule (rolling cap, pause if acceptance drops).
+      - Defines the 02-DOCS ledger path and its columns.
+      - Delegates the actual message copy to cold-outreach.
+      - Names the pipeline handoff point (booked call / warm intro → sales-pipeline).

package/skills/linkedin-outreach/references/ledger-schema.md

@@ -0,0 +1,48 @@
+# Ledger schema
+
+The touch/outcome ledger is the artifact `scripts/verify.sh` checks. One file:
+`02-DOCS/linkedin-outreach/touches.csv`.
+
+## Header (verbatim — verify.sh asserts this exact row)
+
+```csv
+date,name,profile_url,channel,trigger,action,stage,outcome,next_touch
+```
+
+## Columns
+
+| Column | Type | Notes |
+| --- | --- | --- |
+| `date` | ISO date `YYYY-MM-DD` | The day of the touch. |
+| `name` | text | The person. |
+| `profile_url` | URL | LinkedIn profile (de-dupe key). |
+| `channel` | enum | `connect` \| `inmail` \| `dm` \| `comment` \| `view`. |
+| `trigger` | text | The reason you touched: `job_change`, `funding`, `post:<topic>`, `viewed_me`, `referral`. |
+| `action` | text | What you did this touch (e.g. `commented on launch post`, `sent request no-note`). |
+| `stage` | text | Free-text loop stage: `warm`, `requested`, `in_thread`, `handed_off`. |
+| `outcome` | enum (no blanks) | `requested` \| `accepted` \| `replied` \| `conversation` \| `call_booked` \| `dead`. |
+| `next_touch` | ISO date or empty | When to follow up; empty allowed only for terminal outcomes (`call_booked`, `dead`). |
+
+No cell may contain a literal merge token or placeholder (`{first_name}`, `[company]`, `XXXX`, `TODO`) — verify.sh fails on it.
+
+## Filled example
+
+```csv
+date,name,profile_url,channel,trigger,action,stage,outcome,next_touch
+2026-05-26,Marta Ruiz,https://linkedin.com/in/martaruiz,comment,post:attribution,liked + commented on her attribution post,warm,replied,2026-05-28
+2026-05-28,Marta Ruiz,https://linkedin.com/in/martaruiz,connect,post:attribution,sent request no-note,requested,accepted,2026-05-30
+2026-05-30,Marta Ruiz,https://linkedin.com/in/martaruiz,dm,post:attribution,referenced post asked how she splits paid vs organic,in_thread,conversation,2026-06-02
+2026-05-27,Tom Lai,https://linkedin.com/in/tomlai,inmail,job_change,InMail congratulating new RevOps role,requested,accepted,2026-05-30
+2026-06-01,Tom Lai,https://linkedin.com/in/tomlai,dm,job_change,he asked for pricing — booked 20-min call,handed_off,call_booked,
+```
+
+## Weekly-review formulas
+
+Compute over the rows for the period:
+
+- **Acceptance %** = `count(outcome in {accepted,replied,conversation,call_booked}) / count(outcome in {requested,...})` — i.e. accepted-or-better ÷ all requests sent.
+- **Post-accept reply %** = `count(replied|conversation|call_booked) / count(accepted-or-better)`.
+- **Conversations → calls %** = `count(call_booked) / count(conversation|call_booked)`.
+- **Touches/week** = rows whose `date` falls in the week.
+
+Thresholds to act on: acceptance < ~30% → warm harder (phase 2). Reply < ~10% → weak hooks, write a better brief for cold-outreach. Touches/week ≈ 0 → the loop stopped, the real failure.

package/skills/linkedin-outreach/references/sales-navigator-playbook.md

@@ -0,0 +1,61 @@
+# Sales Navigator playbook
+
+Offloaded depth for the **Target** phase. All facts dated 2026-06-02.
+
+## Saved-search filter recipes by ICP archetype
+
+Build from the role and the trigger, not from a name dump. Save the search so Sales Nav re-runs it and surfaces new matches.
+
+| ICP archetype | Core filters to set | Why these |
+| --- | --- | --- |
+| RevOps / Sales Ops leaders at scaling SaaS | Current title = "RevOps", "Sales Operations" (title field, not keyword) · seniority = Manager–VP · headcount 51–500 · `Posted in past 30 days` | Title field avoids matching people who *used to* hold the role; headcount band targets the buy-window. |
+| Ecommerce ops / growth leads | Title = "Ecommerce", "Growth", "DTC" · industry = Retail/Consumer · geography = your serviceable region · `Changed jobs in 90 days` | Job change = new mandate and fresh budget. |
+| Founders / GTM at funded startups | Seniority = Owner/Partner/CXO · `Company funding events` alert on · headcount 11–200 | Funding is the cleanest timing trigger. |
+
+Rule: always add `Posted on LinkedIn in past 30 days`. Active profiles accept and reply at materially higher rates than dormant ones, and a recent post is your warm-up hook.
+
+## Trigger-alert setup
+
+Sales Nav lead/account alerts you should turn on (Core and Advanced):
+
+- **Changed jobs in last 90 days** — new role means new pain and new budget; reach out in the first weeks.
+- **Company funding events** — timing trigger; pair with a relevant, non-salesy congratulations-then-question.
+- **Posted recently** — the post is the thing you engage with in phase 2 before sending the request.
+
+Each alert is a *reason to touch*. Never send a request that can't name its trigger.
+
+## InMail credit economics
+
+- Both Core and Advanced ship **50 InMail credits per month**.
+- Unused credits **roll over up to 3 months** (max **150** accumulated).
+- An InMail that receives a reply **within 90 days** is **credited back** — so a well-targeted InMail can be effectively free.
+
+When InMail beats a connection request:
+
+- The lead is **out of network** and a connection request would sit unseen, or
+- You have **one shot** at a senior buyer and want the longer message format, or
+- The trigger is hot (funding, job change) and you can't afford the 1–2 day warm-up window.
+
+Otherwise prefer the free path: warm up, then send a connection request. InMail credits are scarce; spend them where free reach can't go.
+
+## Advanced-only levers
+
+- **TeamLink** — surfaces warm paths through your colleagues' networks; turns a cold touch into a referral.
+- **Smart Links** — trackable content bundles; you see who opened and how far they read (a buyer-intent signal feeding phase 4).
+- **Buyer-intent signals + Account IQ / Lead IQ** — account-level intent and auto-summaries; useful only at team scale.
+- **CRM sync** — writes activity to the CRM; relevant once sales-pipeline owns the deal.
+
+## Core vs Advanced buy decision (2025 prices)
+
+| | Free | Core | Advanced |
+| --- | --- | --- | --- |
+| Price | $0 | $119.99/mo ($1,079.88/yr) | $159.99/mo ($1,799.88/yr) |
+| 40+ search filters | – | yes | yes |
+| Saved searches + lead/account alerts | – | yes | yes |
+| 50 InMail/mo (rollover→150, reply-refund) | – | yes | yes |
+| Extended profile view | – | yes | yes |
+| TeamLink / Smart Links / buyer-intent / IQ / CRM sync | – | – | yes |
+
+Decision: **Free** if you'll stay disciplined on a tight ICP and don't need alerts. **Core** is the default for a solo working social seller — it pays for itself on saved-search alerts and InMail. **Advanced** only when a team needs TeamLink or a real CRM sync exists; do not buy it for features you won't operate.
+
+*(Sources: business.linkedin.com/sales-solutions/compare-plans; topo.io 2025 price guide; hyperclapper.com Core vs Advanced — accessed 2026-06-02.)*

package/skills/linkedin-outreach/scripts/verify.sh

@@ -0,0 +1,120 @@
+#!/usr/bin/env bash
+#
+# verify.sh — structural guardrail for a LinkedIn-outreach touch ledger.
+#
+# WHAT IT DOES (read-only; never edits or writes a file)
+#   Static, network-free checks over ONE ledger CSV:
+#     1. Header row must equal the required columns EXACTLY:
+#        date,name,profile_url,channel,trigger,action,stage,outcome,next_touch
+#        -> FAIL if it differs.
+#     2. Every data row's `outcome` (column 8) must be in the allowed enum
+#        {requested, accepted, replied, conversation, call_booked, dead}
+#        -> FAIL on any blank or out-of-enum value.
+#     3. No cell may carry a placeholder / merge token:
+#        a "{...}" merge field, a "[...]" slot, "XXXX", or "TODO" -> FAIL.
+#
+#   A missing ledger OR an empty / header-only file exits 0 with a notice
+#   (the skill can be used advisorily before any ledger exists) — never a
+#   false failure.
+#
+# HOW TO RUN (inside YOUR project, not the skills repo)
+#   ./verify.sh                                  # default 02-DOCS/linkedin-outreach/touches.csv
+#   ./verify.sh path/to/touches.csv              # explicit path
+#
+# EXIT CODES
+#   0  clean, or no ledger / empty ledger to check
+#   1  a structural failure (bad header, bad outcome, or placeholder token)
+#   2  bad usage (path given but is a directory)
+#
+# Runs on stock macOS bash 3.2: no mapfile, no associative arrays.
+
+set -euo pipefail
+
+if [ -t 1 ]; then
+  RED=$'\033[31m'; GREEN=$'\033[32m'; YELLOW=$'\033[33m'; NC=$'\033[0m'
+else
+  RED=''; GREEN=''; YELLOW=''; NC=''
+fi
+
+fail_count=0
+ok()   { printf '%s[ ok ]%s %s\n' "$GREEN"  "$NC" "$*"; }
+warn() { printf '%s[warn]%s %s\n' "$YELLOW" "$NC" "$*"; }
+fail() { printf '%s[fail]%s %s\n' "$RED"    "$NC" "$*"; fail_count=$((fail_count + 1)); }
+
+FILE="${1:-02-DOCS/linkedin-outreach/touches.csv}"
+HEADER='date,name,profile_url,channel,trigger,action,stage,outcome,next_touch'
+
+if [ -d "$FILE" ]; then
+  printf '%susage: %s [path/to/touches.csv]%s\n' "$RED" "$0" "$NC"
+  exit 2
+fi
+
+if [ ! -f "$FILE" ]; then
+  warn "no ledger at '$FILE' — nothing to verify (advisory use is fine)"
+  exit 0
+fi
+
+# Strip a possible trailing CR (CRLF files) when reading rows.
+ROW_COUNT="$(awk 'NF{c++} END{print c+0}' "$FILE")"
+if [ "$ROW_COUNT" -eq 0 ]; then
+  warn "ledger '$FILE' is empty — nothing to verify"
+  exit 0
+fi
+
+# --- 1. header row exact match ------------------------------------------------
+ACTUAL_HEADER="$(awk 'NR==1{sub(/\r$/,""); print; exit}' "$FILE")"
+if [ "$ACTUAL_HEADER" = "$HEADER" ]; then
+  ok "header row matches the required schema"
+else
+  fail "header row mismatch"
+  printf '       expected: %s\n' "$HEADER"
+  printf '       found:    %s\n' "$ACTUAL_HEADER"
+fi
+
+DATA_ROWS="$(awk 'NR>1 && NF{c++} END{print c+0}' "$FILE")"
+if [ "$DATA_ROWS" -eq 0 ]; then
+  warn "header-only ledger — no data rows to check yet"
+  printf '\n'
+  if [ "$fail_count" -gt 0 ]; then
+    printf '%s%d failure(s)%s\n' "$RED" "$fail_count" "$NC"; exit 1
+  fi
+  printf '%sall checks passed%s\n' "$GREEN" "$NC"; exit 0
+fi
+
+# --- 2. outcome enum (column 8) -----------------------------------------------
+BAD_OUTCOME="$(awk -F',' '
+  NR>1 && NF>0 {
+    o=$8; gsub(/\r/,"",o); gsub(/^[ \t]+|[ \t]+$/,"",o);
+    allowed="requested accepted replied conversation call_booked dead";
+    if (index(" " allowed " ", " " o " ") == 0) print NR": \""o"\"";
+  }' "$FILE")"
+if [ -n "$BAD_OUTCOME" ]; then
+  while IFS= read -r line; do
+    [ -n "$line" ] && fail "row $line — outcome not in {requested,accepted,replied,conversation,call_booked,dead}"
+  done <<EOF
+$BAD_OUTCOME
+EOF
+else
+  ok "every data row has a valid outcome"
+fi
+
+# --- 3. placeholder / merge-token banlist -------------------------------------
+PLACEHOLDERS="$(grep -nE '\{[^}]*\}|\[[^]]*\]|XXXX|TODO' "$FILE" 2>/dev/null || true)"
+if [ -n "$PLACEHOLDERS" ]; then
+  while IFS= read -r line; do
+    [ -n "$line" ] && fail "placeholder/merge token present at line ${line%%:*} — fill before logging"
+  done <<EOF
+$PLACEHOLDERS
+EOF
+else
+  ok "no placeholder / merge tokens in any cell"
+fi
+
+# --- summary ------------------------------------------------------------------
+printf '\n'
+if [ "$fail_count" -gt 0 ]; then
+  printf '%s%d failure(s)%s\n' "$RED" "$fail_count" "$NC"
+  exit 1
+fi
+printf '%sall checks passed%s\n' "$GREEN" "$NC"
+exit 0