proposal-win-loss-review
Skill5 starsChanged 4 months agoMITView on GitHub
Learns from won and lost deals to fix upstream targeting and messaging. Use when a run of losses feels similar, or when you keep reaching proposal stage with people who never buy.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ad-to-landing-promise-matchSkill
- b2b-audience-signal-auditSkill
- cold-outbound-sequence-reviewSkill
- competitor-lead-angle-reviewSkill
- crm-lead-source-quality-auditSkill
- discovery-call-gap-analysisSkill
- disqualification-reason-minerSkill
- email-nurture-sequence-reviewSkill
- form-friction-finderSkill
- ghosted-after-the-demoSkill
- google-ads-lead-quality-auditSkill
- icp-reality-checkSkill
- landing-page-qualification-reviewSkill
- lead-magnet-offer-fitSkill
- lead-scoring-sanity-checkSkill
- lead-to-opportunity-drop-off-reviewSkill
- linkedin-ads-lead-quality-auditSkill
- meeting-prep-five-minutesSkill
- meta-ads-lead-quality-auditSkill
- objection-cheat-sheetSkill
- pipeline-hygiene-auditSkill
- sales-follow-up-speed-auditSkill
- scale-readiness-check-lead-genSkill
- sdr-handoff-brief-generatorSkill
- spam-folder-checkSkill
- weekly-b2b-lead-gen-readoutSkill
- what-to-say-to-this-companySkill
- won-deal-to-case-studySkill
- write-the-follow-upSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use the shared quality bar in ../references/output-standard.md and ../references/skill-design-principles.md when those files are available.
- Distinctive: line 16
Do not use this skill for broad lead-generation advice without source, CRM, sales or qualification evidence.
- Distinctive: line 24
If an input is missing, continue with a clearly marked assumption instead of inventing data.
- Distinctive: line 36
If the data does not connect to revenue, pipeline, qualified leads or conversion quality, label the recommendation as a hypothesis.
- Distinctive: line 37
If platform metrics and downstream data disagree, trust the downstream source for business quality and platform data for delivery mechanics.
- Distinctive: line 38
If the issue could be tracking, offer, audience, page or follow-up, do not collapse it into one cause without evidence.
- Distinctive: line 39
Do not recommend more budget until lead quality, follow-up and tracking confidence are separated.
- Distinctive: line 61
Do not make changes to live campaigns, pages, tags, containers, CRM fields or customer messages.
- Distinctive: line 62
Do not claim performance impact without evidence.
- Distinctive: line 64
Keep recommendations practical for a performance operator, founder or owner with a real advertising problem.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Proposal Win Loss Review
Use the shared quality bar in ../references/output-standard.md and ../references/skill-design-principles.md when those files are available.
Use this skill when
- the user shares lead source, CRM stage, sales note, form, landing page or campaign data tied to proposal win loss review.
- the next decision could change targeting, qualification, scoring, follow-up, sales handoff or budget.
- lead volume looks acceptable but SQL, opportunity, closed-won, rejection or response-speed data raises doubt.
Do not use this skill for broad lead-generation advice without source, CRM, sales or qualification evidence. Use it when a real B2B lead quality decision is on the table.
Required input
- business model, ICP, offer, ACV or deal value range, sales cycle and main conversion goal.
- ad, landing page, lead form, CRM, call note, email or campaign data relevant to this diagnostic.
- time window, traffic source, lead volume and downstream outcomes where available.
- what decision the user is trying to make next: create, fix, scale, pause, brief sales or investigate.
- If an input is missing, continue with a clearly marked assumption instead of inventing data.
Analysis workflow
- Collect won/lost proposal notes, source, segment, deal size, competitor, objections and close reason.
- Cluster win/loss reasons into fit, pain, pricing, authority, timing, proof, implementation, competitor and trust.
- Map repeated loss reasons back to lead source, ad promise, page promise and qualification step.
- Identify which upstream messages attract deals you can actually win.
- Recommend targeting, proof, offer, qualification or sales collateral changes.
Decision rules
- If the data does not connect to revenue, pipeline, qualified leads or conversion quality, label the recommendation as a hypothesis.
- If platform metrics and downstream data disagree, trust the downstream source for business quality and platform data for delivery mechanics.
- If the issue could be tracking, offer, audience, page or follow-up, do not collapse it into one cause without evidence.
- Do not recommend more budget until lead quality, follow-up and tracking confidence are separated.
Output format
| Finding | Evidence | Lead quality impact | Recommended action | Confidence |
| Specific diagnostic claim | Data, screenshot, report, note or missing-data marker | Business or signal consequence | Smallest useful next step and owner | High / Medium / Low |
End with:
Decision:fix / test / monitor / ask for data / do not act yetApproval needed:yes/no and what would change if approvedMissing data:only the inputs that would materially change the recommendation
Practical example
User: "Here are CRM stages, source data and sales notes for proposal win loss review. What should we change before the next campaign move?"
Assistant should: find the pattern the losses share, trace it upstream to targeting or messaging, and stop at what to change before the next proposal.
Guardrails
- Do not make changes to live campaigns, pages, tags, containers, CRM fields or customer messages.
- Do not claim performance impact without evidence.
- Mark missing data clearly.
- Keep recommendations practical for a performance operator, founder or owner with a real advertising problem.
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.

