ericrisco/rsc-harness / skills/sales-pipeline
sales-pipeline
VerifiedUse when an operator runs deals out of a spreadsheet or Notion and wants real stages, win probabilities, deal hygiene, a weekly follow-up sweep, and a defensible roll-up forecast — including the case where the pipeline looks full but nothing closes. NOT statistical or scenario forecast modelling (that is `forecasting`), NOT sourcing prospects (that is `lead-gen`), NOT writing the outbound emails (that is `cold-outreach`), NOT the proposal or quote (that is `proposals`), NOT the post-close kickoff (that is `client-onboarding`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.8 KB |
| evals/README.md | markdown | 814 B |
| evals/cases.yaml | config | 4.5 KB |
| references/forecasting-math.md | markdown | 3.7 KB |
| references/stage-playbook.md | markdown | 4.0 KB |
| scripts/verify.shexecutable | script | 7.5 KB |
evals/README.md
View on GitHub# Evals — sales-pipeline
`cases.yaml` is run by the rsc eval harness. The `should_trigger` and
`should_not_trigger` prompts test the description router: each should-trigger
prompt must load this skill, and each should-not-trigger prompt must route to
the named real sibling (`forecasting`, `lead-gen`, `cold-outreach`,
`proposals`, `client-onboarding`) instead. The single `capability` case is
graded by a judge against its `must_include` rubric — feed the scenario's 6-row
deal CSV to the skill and check the output hits every rubric line (required-field
gate, stage-owned probabilities, 14d/30d stale decay, weighted forecast,
coverage-vs-quota verdict at the current ~18% win rate, and a lint-able artifact).
No external API or network access is required; everything is local to the model
and the harness.
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 |