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 |
evals/cases.yaml
View on GitHubskill: 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).
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 |