ericrisco/rsc-harness / skills/linkedin-outreach
linkedin-outreach
VerifiedUse when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning profile views and post engagers into warm threads, logging every touch. NOT the note or DM copy (that is `cold-outreach`), NOT the deal after a reply (that is `sales-pipeline`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| evals/README.md | markdown | 918 B |
| evals/cases.yaml | config | 2.8 KB |
| references/ledger-schema.md | markdown | 2.7 KB |
| references/sales-navigator-playbook.md | markdown | 3.8 KB |
| scripts/verify.shexecutable | script | 4.2 KB |
references/ledger-schema.md
View on GitHub# 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |