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/README.md
View on GitHub# 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.
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 |