New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sales Pipeline

by ericrisco in ericrisco/rsc-harness

A skill your agent uses 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…

MITAuto-check passedSales & Support

Install Sales Pipeline

skills CLI
$ npx skills add ericrisco/rsc-harness --skill sales-pipeline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness sales-pipeline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales-pipeline .claude/skills/sales-pipeline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sales-pipeline
GitHub stars
180
Token cost
~3.3k tokens
SKILL.md length
1,645 words
Files
6 (incl. scripts, references)
Skills in repo
233
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • An operator runs deals out of a spreadsheet
  • SKILL.md covers When to use / when NOT, The artifact first — the…, The stage model — small,… and Deal hygiene — the…, plus 4 more sections
  • Runs Shell scripts from its folder
  • Notion and wants real stages

What it does

Sales Pipeline is an agent skill from ericrisco/rsc-harness. Use 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…

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/forecasting-math.md`).

It sits in Sales & Support, covering CRM management, Forecasting and time series and Proposals and quotes. It works with Notion. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • An operator runs deals out of a spreadsheet
  • Notion and wants real stages
  • Win probabilities
  • A weekly follow-up sweep

Example prompts

  • “/sales-pipeline”

Requirements

  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit 1f8d9bb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sales Pipeline loads about 3.3k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 137 tokens; SKILL.md has 1,645 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~137
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit 1f8d9bb, republished under its MIT licence (© ericrisco). 1,645 words, ~3,255 tokens.

Download SKILL.mdSave it as .claude/skills/sales-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
sales-pipeline
description
Use 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`).
tags
sales, crm, pipeline, forecasting, deal-hygiene, business-ops
recommends
forecasting, lead-gen, cold-outreach, proposals, client-onboarding, spreadsheet-ops
origin
risco

Sales Pipeline — A Disciplined CRM Out of a Flat File

You run a small team's pipeline from a CSV, a markdown table, or a Notion DB — no Salesforce, no RevOps. Your one rule: the forecast is what the gated stages and current win rates say, not what the rep hopes. Happy-ears deals do not inflate the number on your watch.

This skill does four jobs and refuses to drift into the siblings that own the rest: (1) define a small set of gated stages with objective exit criteria, (2) keep every open deal hygienic (next step + close date + last-touch, flag the stale), (3) run a weekly follow-up sweep, and (4) roll a defensible weighted forecast with a coverage ratio. The heavy statistical modeling, the lead sourcing, the outbound copy, the proposal, the post-close handoff — each belongs to a sibling. Route, do not improvise their job.

When to use / when NOT

Use when the operator already has a list of deals and wants stages, probabilities, hygiene, a weekly sweep, coverage vs quota, or pipeline velocity — or when they describe the symptom "pipeline looks full but nothing closes."

Do NOT use when the ask is one of these — route to the owner:

The askOwnerWhy it is not here
3-scenario revenue model, seasonality, cohort/time-series projectionforecastingThat is the statistical/scenario layer. This skill only does the simple stage-weighted roll-up that falls out of the pipeline.
Find / scrape / qualify NEW prospect companies to addlead-genThis skill operates on deals that already exist in the list.
Write the cold email or follow-up sequence to contact a prospectcold-outreachThis skill schedules the next step; it does not write the words.
Write the proposal / quote / SOW for a qualified dealproposalsA stage transition is not a document.
Post-close kickoff, account setup, onboardingclient-onboardingThe moment a deal is Closed-Won it leaves this skill.
Generic dashboard / charting of arbitrary metrics, KPI tree designdashboard / kpi-frameworkThis skill emits pipeline numbers, not a charting layer.

The boundary worth memorizing: forecasting owns the math models; sales-pipeline owns the operational CRM. When the request needs Monte Carlo, regression, or scenario trees, hand it over.

The artifact first — the deal-record schema

Everything below lints against one table. Define it before anything else, because hygiene, the sweep, and the forecast are all just operations on these columns. One deal = one row. Required columns:

columnmeaningrule
idstable deal idunique, never reused
companythe account—
valuedeal value (one currency, document which)number, no symbols
stagecurrent stagefrom the allowed set (next section)
win_probstage win-probability as a decimal0–1, owned by the stage, not the rep
weighted_valuevalue × win_probmust equal the product (lint enforces it)
close_dateexpected close (ISO YYYY-MM-DD)required on every open deal
next_stepthe next concrete action + its daterequired on every open deal
last_touchdate of last real activity (ISO)required on every open deal
ownerwho owns the deal—
forecast_categoryPipeline / Best Case / Commit / Closed / Omitteda category, not a stage

One good open row (CSV):

csv
id,company,value,stage,win_prob,weighted_value,close_date,next_step,last_touch,owner,forecast_category
D-104,Acme,40000,Discovery,0.30,12000,2026-07-15,"2026-06-09 demo with VP Eng",2026-05-30,Dana,Best Case

Hard rule, no exceptions: no open deal may be missing next_step, close_date, or last_touch. A deal with no next step is not a deal, it is a wish. The sweep and the forecast both treat a missing field as a defect, not a blank.

The stage model — small, gated, stage-owned probability

Default to six stages. Five stages with clear exit criteria beat nine stages with none. Each stage advances only on an objective, verifiable buyer action — never on rep optimism.

stagedefault win_probexit criterion (the verifiable buyer action that advances it)
Prospecting0.05Buyer agreed to a first real conversation (meeting on the calendar).
Qualification0.10BANT/MEDDIC documented "yes" — budget, authority, need, timeline confirmed.
Discovery0.30Buyer confirmed the problem + success criteria; you have the buying process and review layers.
Proposal/Demo0.40Proposal or demo delivered and acknowledged; buyer engaged on it.
Negotiation0.65Terms/price under active discussion; verbal intent + a mutual close plan.
Closed1.0 / 0.0Signed (Won) or formally lost (Lost).

Rules that make the table hold:

  • Probability belongs to the stage, not the deal. A rep who hand-sets one deal to 90% in Discovery is sandbagging or happy-ears; both poison the forecast. The stage carries the number, uniformly. (Why: it removes the single biggest source of forecast inflation in small teams.)
  • No stage advances without its exit criterion met AND a calendared next step. "If you don't know the criteria, timeline, review layers and legal steps, the close date is a guess."
  • Negotiation 50–80% is a band, not a default 80. Pick within the band on real signal (legal in motion → higher); never max it out reflexively.

Qualification gate: run BANT as a ~60-second screen for small deals; switch to MEDDIC/SPICED above ~$25K ACV. The full six-stage playbook — every exit criterion, required fields per stage, the BANT-vs-MEDDIC pillars, and the forecast-category mapping — lives in references/stage-playbook.md.

Deal hygiene — the required-field gate and the stale rules

Roughly 40–60% of B2B CRM pipeline is stale (no progression in 30+ days). A forecast built on a stale list is fiction. Apply an activity-decay model on every open deal:

conditionaction
Missing next_step / close_date / last_touchDefect — flag, do not forecast until fixed.
No touch for 14+ daysHalve the deal's effective weight in the forecast.
No touch for 30+ daysExclude from coverage entirely (treat as stale, not pipeline).
Sitting > 1.5× the average time-in-stageFlag for review — it is stuck.
close_date already in the past, deal still openFlag — the date is a lie; re-set or disqualify.

Bad → Good on a single row:

text
BAD  (open, but a wish dressed as a deal — fails the gate):
  D-220,Globex,60000,Proposal,0.80,48000,,,,Sam,Commit
  ^ win_prob hand-set to 0.80 in Proposal, no close_date, no next_step,
    no last_touch, Commit category on zero evidence.

GOOD (gated, hygienic, stage-owned probability):
  D-220,Globex,60000,Proposal,0.40,24000,2026-08-01,"2026-06-12 send revised SOW",2026-06-02,Sam,Best Case
  ^ win_prob = stage default, weighted_value recomputed, dated next step,
    fresh last_touch, category demoted to match the evidence.
Show full SKILL.md (716 more words)Show less

The weekly follow-up sweep

Build hygiene into a ~45-minute WEEKLY pipeline review, not a quarterly cleanup — stale deals compound fast and a quarterly purge always finds the rot too late. The sweep is a fixed checklist; run it and emit a prioritized follow-up list:

  • Every open deal has next_step + close_date + last_touch — list the defects first.
  • Stale: no touch 14+ days (halve) and 30+ days (drop) — surface both buckets.
  • close_date in the past on an open deal — re-set or disqualify.
  • Slipped: close_date pushed two weeks in a row — flag; two slips is a pattern, not noise.
  • Stuck: time-in-stage > 1.5× the average for that stage.
  • Output: a ranked follow-up list (highest weighted_value × most stale first), each with the one concrete next action and its date.

Track coverage as a 4-week rolling trend, not a single snapshot. Two consecutive weeks of declining coverage with no closes is a red flag — escalate, do not wait for quarter-end.

The forecast roll-up

Three numbers fall out of a clean pipeline. Compute them; do not model beyond them (that is forecasting).

Weighted forecast = Σ over open deals of value × stage win_prob. Apply the stale decay first (halve at 14d, drop at 30d) so the number reflects live pipeline, not the wish list.

Pipeline coverage ratio = Total Qualified Pipeline Value ÷ Revenue Target. Read it against the segment, because win rates differ:

segmentACV / win ratecoverage mincoverage target
Enterprise$100K+ / 15–20% win5×6–7×
Commercial$25–100K / 20–30%3.5×4–5×
SMB<$25K / 30–40%2.5×3–4×

Pipeline velocity = (Open opps × Avg deal size × Win rate) ÷ Sales-cycle length (days) → dollars/day. Cycle length has the most leverage: a ~20% cut in cycle length lifts velocity ~25%.

Forecast categories are not stages — map them separately: Pipeline / Best Case / Commit / Closed / Omitted. As a sanity expectation, roughly ~25% of "Pipeline", a third-to-half of "Best Case", and near-all of "Commit" typically lands in-quarter.

The current-win-rate caveat — non-negotiable. 2025 benchmarks moved against sellers: B2B win rates fell ~21% → ~18% and cycles lengthened ~12% YoY. Forecast with the current ~18% win rate and your real cycle length, never last year's optimistic numbers. A 24-month-old win rate is the quietest way to over-forecast.

Worked examples — weighted forecast on a 5-deal list, coverage by segment, velocity, and the exact column contract verify.sh enforces — are in references/forecasting-math.md.

Anti-patterns

Anti-patternWhy it failsDo instead
Rep hand-sets win_prob per dealHappy-ears/sandbagging inflate the forecast; the number stops being comparableProbability is owned by the stage, applied uniformly
Stages with no exit criteria"Discovery" becomes a place deals go to die; no one can verify progressionEvery stage gates on an objective buyer action
Counting stale deals (30+ days no touch) in coverage40–60% of pipeline is stale; coverage looks healthy while nothing movesDrop 30d+ from coverage, halve 14d+, flag stuck deals
Forecasting off list price, not weighted valueTreats a Qualification deal like a signed one; massive over-forecastvalue × stage win_prob, decayed for staleness
Quarterly cleanup instead of weeklyRot is found three months too late; the quarter is already lost45-min weekly sweep; 4-week rolling coverage trend
Using a 24-month-old win rate2025 win rates fell to ~18%, cycles +12%; old numbers over-forecastUse the current win rate and your real cycle length
forecast_category set to "Commit" on a Discovery dealCategory drifts from evidence; the commit number becomes a fantasyCategory must match documented evidence, not hope
Nine micro-stages "for granularity"More stages, less discipline; reps can't tell them apartSix gated stages beat nine ungated ones
Open deal with no next_stepIt is a wish, not a deal; it silently ages into stalenessNo next step → it is a defect, surface it in the sweep

References and siblings

  • references/stage-playbook.md — the six stages in full, exit criteria, required fields per stage, BANT-vs-MEDDIC, forecast-category mapping.
  • references/forecasting-math.md — worked weighted-forecast / coverage / velocity examples and the verify column contract.

Siblings that own the adjacent jobs — route to them by name: ../forecasting/SKILL.md (the math models), ../lead-gen/SKILL.md (sourcing), ../cold-outreach/SKILL.md (the outbound copy), ../proposals/SKILL.md (the quote/SOW), ../client-onboarding/SKILL.md (post-close). For wiring the list to Sheets/Notion or bulk edits, ../spreadsheet-ops/SKILL.md.

To lint a pipeline file you produced — required columns, required fields on open deals, stage names in the allowed set, win_prob in range, weighted_value == value × win_prob, and a coverage line present — run scripts/verify.sh path/to/pipeline.csv (read-only; a clean or empty file exits 0).

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/sales-pipeline of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/forecasting-math.md
  • references/stage-playbook.md
  • scripts/verify.sh

Open the folder on GitHubat commit 1f8d9bb

Compare with similar skills

Sales Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sales Pipeline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sales Pipeline this skillericrisco/rsc-harness180—~3.3kAutomated safety check: PassMIT
B2B Lead Generationminhnv0807/ai-business-skills609—~1.2kAutomated safety check: PassMIT
Account ExecutiveaAAaqwq/AGI-Super-Team1051 repos~3.4kAutomated safety check: PassMIT
Suede RevopsJasonColapietro/suede-creator-skills127—~3.8kAutomated safety check: PassMIT
Lead Gen Tool Builderexplorium-ai/gtm-skills185—~1.8kAutomated safety check: NotesMIT
Lead-to-Payment Sales Flowhewi333/Mom-n-Pop-Skills122—~2.8kAutomated safety check: NotesMIT

Similar skills

  • B2B Lead Generation

    minhnv0807/ai-business-skills

    Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.

    609 GitHub stars~1.2k tokensUpdated 28 days ago
    Sales & SupportAuto-check passed

  • Account Executive

    aAAaqwq/AGI-Super-Team

    Expert sales execution covering pipeline management, discovery, demos, negotiation, and deal closing.

    105 GitHub starsUsed in 1 repo~3.4k tokens
    Sales & SupportAuto-check passed

  • Suede Revops

    JasonColapietro/suede-creator-skills

    Suede-owned revenue-operations discipline. An agent skill from JasonColapietro/suede-creator-skills.

    127 GitHub stars~3.8k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Lead Gen Tool Builder

    explorium-ai/gtm-skills

    Lead generation tool builder skill for Claude Code and Codex: scaffolds a complete, self-hostable, ZoomInfo-style B2B lead-generation web app — company & contact search UI, firmographic and…

    185 GitHub stars~1.8k tokensUpdated 2 days ago
    Sales & SupportAuto-check: notes

  • Lead-to-Payment Sales Flow

    hewi333/Mom-n-Pop-Skills

    Runs a small service business lead from intake through estimate, owner approval over Telegram, Stripe payment link and customer email draft to payment tracking.

    122 GitHub stars~2.8k tokensUpdated 29 days ago
    Sales & SupportAuto-check: notes

  • AI SDR Deployment

    tech-leads-club/agent-skills

    Guides founders and sales teams through choosing, deploying and tuning AI sales development reps, from signal-based targeting to human handoff.

    7k GitHub stars~4.4k tokensUpdated yesterday
    Sales & SupportAuto-check passed

More from ericrisco/rsc-harness

All 233 skills in this repo

  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    180 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    180 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    180 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    180 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    180 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    180 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Sales Pipeline

What does Sales Pipeline do?

A skill your agent uses 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…. Sales Pipeline is an agent skill from ericrisco/rsc-harness. Use 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.

When should I use Sales Pipeline?

Sales Pipeline fits situations like: an operator runs deals out of a spreadsheet; notion and wants real stages; win probabilities; A weekly follow-up sweep.

How do I install Sales Pipeline in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill sales-pipeline -a claude-code`. Or copy the skill folder (skills/sales-pipeline in ericrisco/rsc-harness) into .claude/skills/sales-pipeline in your project. Claude Code loads it when a task matches its description.

How do I install Sales Pipeline in Codex?

Run `npx skills add ericrisco/rsc-harness --skill sales-pipeline -a codex`. Or copy the skill folder (skills/sales-pipeline in ericrisco/rsc-harness) into .agents/skills/sales-pipeline in your project. Codex loads it when a task matches its description.

Can I use Sales Pipeline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill sales-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-pipeline, .gemini/skills/sales-pipeline, .github/skills/sales-pipeline and .opencode/skills/sales-pipeline in your project.

What does Sales Pipeline need to run?

Going by SKILL.md and its folder, Sales Pipeline needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Sales Pipeline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sales Pipeline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sales Pipeline use?

Sales Pipeline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sales Pipeline use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to Sales Pipeline?

Skills that share tags, products or a category with Sales Pipeline: B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Account Executive (aAAaqwq/AGI-Super-Team, 105 stars), Suede Revops (JasonColapietro/suede-creator-skills, 127 stars) and Lead Gen Tool Builder (explorium-ai/gtm-skills, 185 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sales Pipeline?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 180 GitHub stars. The repository holds 233 skills in this directory. The repository was last updated on October 9, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.