sales-pipeline
Skill1 starsChanged 46 days agoMITView on GitHub
Use this skill for sales work - "prospek", "lead", "follow up klien", "buat proposal", "penawaran/quotation", "nego harga", "closing", pipeline review, or qualifying whether an opportunity is worth pursuing. Do NOT use for mass-audience marketing content (use marketing-growth) or invoice/AR work (use finance-analyst).
4 other projects use a version of this.
Adopted by
Most recently taken up by
- manusco/resonancetheir own version, first seen Oct 22, 2026
- ericosiu/ai-marketing-skillstheir own version, first seen Sep 2, 2026
- varunk130/ai-marketing-claude-skillstheir own version, first seen May 18, 2026
- admdanielpaulino/claude-codestheir own version, first seen Apr 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ericosiu/ai-marketing-skills★ 3.8ksame name
- manusco/resonance★ 38same name
- admdanielpaulino/claude-codes★ 1same name
- varunk130/ai-marketing-claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accounting-coreSkill
- admin-opsSkill
- agent-skill-authorSkill
- code-review-hardeningSkill
- content-creatorSkill
- content-editorSkill
- continuous-learningSkill
- coo-orchestratorSkill
- finance-analystSkill
- hr-adminSkill
- hr-officerSkill
- incident-debuggingSkill
- marketing-growthSkill
- prd-creatorSkill
- principal-engineeringSkill
- product-designerSkill
- project-auditSkill
- project-timeline-creatorSkill
- sdlc-masterSkill
- secure-deploy-opsSkill
- social-media-specialistSkill
- strategic-approachSkill
- tech-scoutSkill
- uiux-engineerSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Never pitch before the pain is quantified - the pain number becomes your pricing anchor.
- Distinctive: line 44
Never discount without removing scope or changing terms (prepayment, longer commitment, testimonial).
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sales Pipeline
Sell the outcome, qualify hard, and always leave with a next step that has a date.
Lead qualification (score before investing time)
Score 0-2 each; pursue at ≥ 6/10, nurture 4-5, drop < 4:
- Budget: can they pay in your price range? Any signal (company size, current spend)?
- Authority: talking to the decision maker, or know who is?
- Need: pain is explicit and costs them money/time today (not "nice someday").
- Timeline: an event forces a decision (deadline, contract ending, launch)?
- Fit: you can genuinely deliver this well - overselling kills referrals.
Log the score and the evidence, not just the number.
Discovery call / chat - get these answers
- What are they doing today, and what does the current way cost them (hours, money, missed revenue)?
- What triggered them to look for a solution now?
- What does success look like in 90 days, in their words?
- Who else is involved in the decision, and what does that person care about?
- Budget range and decision timeline.
Never pitch before the pain is quantified - the pain number becomes your pricing anchor.
Proposal structure (short beats long)
1. Situasi & masalah (dalam kata-kata klien, dengan angka biaya masalahnya)
2. Solusi & scope - deliverable konkret, apa yang TIDAK termasuk
3. Hasil yang diukur (target 90 hari)
4. Timeline & milestone
5. Investasi: 2-3 opsi paket (anchor tinggi dulu), syarat bayar
6. Langkah berikutnya + masa berlaku penawaranScope exclusions are mandatory - undefined scope is where projects die.
Follow-up cadence (default; adapt to signals)
D+2 → D+7 → D+14, then monthly nurture. Each follow-up adds value (relevant insight, case, answer to their question) - never a bare "gimana kabarnya?". Three no-responses → move to nurture, tell them the door stays open.
Negotiation rules
- Never discount without removing scope or changing terms (prepayment, longer commitment, testimonial).
- Silence after stating price. First concession smallest.
- Walk-away point decided before the call.
Pipeline review format
Per deal: stage · value · qualification score · next step + date · risk. Flag any deal with no dated next step - that's not a deal, it's a wish.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.