Skip to content

ericrisco/rsc-harness / skills/linkedin-outreach

linkedin-outreach

Verified

Use 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`).

FileKindSize
SKILL.mdskill md11.1 KB
evals/README.mdmarkdown918 B
evals/cases.yamlconfig2.8 KB
references/ledger-schema.mdmarkdown2.7 KB
references/sales-navigator-playbook.mdmarkdown3.8 KB
scripts/verify.shexecutablescript4.2 KB

references/sales-navigator-playbook.md

View on GitHub
# 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.)*
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall