[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QP3DK18WKA8P3BQMVA19X6":3,"skill-same:01M6QP3DK18WKA8P3BQMVA19X6":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":14,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6QP3DK18WKA8P3BQMVA19X6","rfp-responder",null,"Use when an RFP, RFI, RFQ, security questionnaire, vendor questionnaire, or proposal request arrives and the team needs a structured response — parsing multi-section buyer-dictated requirements (MANDATORY vs WEIGHTED vs NICE-TO-HAVE), building a Shipley-method proof-point matrix mapping each requirement to a verifiable proof point, articulating 3-5 win-themes that ladder up across requirements, and producing a Shipley-derived winrate estimate that informs a bid \u002F no-bid \u002F partner-bid recommendation. For Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers at the response-strategy moment. Surfaces GAP requirements explicitly — never invents claims. NOT free-form proposal narrative authoring, NOT contract redline, NOT marketing collateral.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frfp-responder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"Responder","rfp responder","rfp","at","security","matrix","form","narrative","themes","free","authoring","bid-management","structured-response","proof-points","win-theme","shipley","rfq","rfi","redline","team","2026-11-10 10:12:30",false,"---\nname: rfp-responder\ndescription: \"Use when an RFP, RFI, RFQ, security questionnaire, vendor questionnaire, or proposal request arrives and the team needs a structured response — parsing multi-section buyer-dictated requirements (MANDATORY vs WEIGHTED vs NICE-TO-HAVE), building a Shipley-method proof-point matrix mapping each requirement to a verifiable proof point, articulating 3-5 win-themes that ladder up across requirements, and producing a Shipley-derived winrate estimate that informs a bid \u002F no-bid \u002F partner-bid recommendation. For Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers at the response-strategy moment. Surfaces GAP requirements explicitly — never invents claims. NOT free-form proposal narrative authoring, NOT contract redline, NOT marketing collateral.\"\ncontext: fork\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [commercial, rfp, rfi, rfq, shipley, win-theme, proof-points, structured-response, bid-management]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# rfp-responder\n\n## Purpose\n\nHelp Bid Managers, Proposal Leads, and Directors of Sales answer five questions at the response-strategy moment:\n\n1. **What is this RFP actually asking?** (parse sections, tag every requirement MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints)\n2. **What is our true fit?** (proof-point matrix per requirement: STRONG \u002F PARTIAL \u002F GAP, each backed by a verifiable source — case study, certification, customer quote, technical attestation, benchmark)\n3. **What is our win-theme strategy?** (Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets)\n4. **What is our realistic winrate?** (Shipley-derived factor model: fit, incumbent, relationship strength, decision-criteria alignment, late-entry, competitor count, deal size — produces estimate + confidence band)\n5. **Should we bid?** (deterministic verdict: BID \u002F PARTNER-BID \u002F NO-BID with named factors driving the call)\n\nThe skill surfaces GAPs explicitly. Leadership decides whether to close them, partner around them, or no-bid. **It never invents claims.**\n\n## When to use\n\n- A 30+ page RFP \u002F RFI \u002F RFQ has landed with a 7-14 day response deadline\n- A security questionnaire (SIG, CAIQ, custom-buyer) needs structured Q&A — not prose\n- The team is preparing a bid \u002F no-bid review and needs a defensible winrate estimate\n- Sales Engineering has a proof-point library but no system to map proofs to requirements\n- Leadership wants to see fit % (STRONG \u002F PARTIAL \u002F GAP) before committing pursuit budget\n- A late-entry opportunity needs honest assessment of the relationship deficit\n\n**Do not use for:**\n- Free-form proposal narrative authoring → `business-growth\u002Fcontract-and-proposal-writer`\n- Contract redline AFTER award → `c-level-advisor\u002Fgeneral-counsel-advisor`\n- Marketing collateral \u002F category content → `marketing-skill\u002F*`\n- Discount approval on the awarded deal → `commercial\u002Fdeal-desk`\n- Pricing-model design for a new product → `commercial\u002Fpricing-strategist`\n\n## Workflow\n\n### Step 1 — Parse the RFP\n\nDrop the RFP markdown \u002F text into `scripts\u002Frfp_parser.py`. Output: structured JSON listing every requirement, tagged MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE based on cue words (must \u002F shall = MANDATORY; should \u002F weighted scoring numbers = WEIGHTED; may \u002F preferred \u002F desired = NICE-TO-HAVE). Captures section structure, scoring criteria if disclosed, deadline, submission format constraints.\n\n```bash\npython scripts\u002Frfp_parser.py --input rfp.md --output json > parsed.json\n```\n\n### Step 2 — Score fit per requirement\n\nFill `assets\u002Frfp_intake_template.md` with your proof-point library (each proof tagged with type + verifiable source + which requirement-tags it covers) and proposed win-themes. Feed parsed RFP + intake into `scripts\u002Fresponse_drafter.py`. Output: proof-point matrix per requirement with STRONG \u002F PARTIAL \u002F GAP, win-theme injection, GAP audit.\n\n```bash\npython scripts\u002Fresponse_drafter.py --input draft_input.json --output markdown > matrix.md\n```\n\n**Hard rule:** GAP requirements are surfaced, never invented around. Leadership reads the GAP audit and decides: close the gap, partner-bid, or no-bid.\n\n### Step 3 — Apply win-theme strategy\n\nShipley method: 3-5 themes that span requirements. Each theme answers \"why us over the incumbent \u002F competitor on the criteria the buyer named.\" `response_drafter.py` shows which themes thread through which requirements — a theme appearing in \u003C2 requirements is decorative, not strategic, and gets flagged.\n\n### Step 4 — Estimate winrate\n\nFeed deal context (fit %, incumbent strength, relationship, decision-criteria alignment, late-entry, competitor count, deal size vs. average) into `scripts\u002Fwinrate_predictor.py`. Output: Shipley-derived estimate 0-100% + confidence band + factor breakdown + BID \u002F PARTNER-BID \u002F NO-BID verdict.\n\n```bash\npython scripts\u002Fwinrate_predictor.py --input deal_context.json --profile enterprise-software --output markdown\n```\n\n**No-bid threshold:** estimate \u003C 20% triggers automatic no-bid recommendation.\n\n### Step 5 — Decide\n\nTake parsed RFP + proof-point matrix + GAP audit + winrate estimate into the go \u002F no-go review. Skill does not commit pursuit budget — leadership does.\n\n## Scripts\n\n- `scripts\u002Frfp_parser.py` — section + requirement extractor (regex + cue-word heuristics, stdlib only)\n- `scripts\u002Fresponse_drafter.py` — proof-point matrix + win-theme injection + GAP audit\n- `scripts\u002Fwinrate_predictor.py` — Shipley-derived factor model + bid\u002Fno-bid verdict, industry-profile-tuned\n\nAll scripts: stdlib only (argparse, json, sys, pathlib, re, collections, statistics). `--help` and `--sample` work on all three.\n\n## References\n\n- `references\u002Fshipley_method_canon.md` — Shipley Proposal Guide v6, Shipley Capture Guide, APMP BoK, Tom Sant, Tom Searcy + Henry DeVries, Strategic Proposals research, Larry Newman\n- `references\u002Frfp_strategy_canon.md` — FAR, GSA, Forrester, Gartner, Bain, McKinsey, B2B International on RFP win-rates and buyer behavior\n- `references\u002Frfp_anti_patterns.md` — Shipley failure modes, APMP cases, Strategic Proposals research, federal loss reviews, MIT Sloan, Bain commercial-discipline, Gartner\n\n## Assumptions\n\n- **The RFP is the ground truth.** If the buyer asked it, answer it — in the order they asked, in the format they specified. Re-organizing for narrative flow is for proposals, not RFPs.\n- **Proof points must be verifiable.** A claim is only as strong as the case study, certification, customer reference, or technical attestation backing it. Unsourced claims become GAPs.\n- **Win-themes are buyer-side, not seller-side.** \"We're the leader in X\" is a marketing claim; \"Your operations team reduces incident MTTR by 60% with the same headcount\" is a win-theme. Shipley canon, not optional.\n- **Winrate estimates are directional.** The model is a discipline tool to force honest pursuit-qualification — not an oracle. Confidence band always wider than the point estimate suggests.\n- **Industry profiles tune base rates** — government RFPs reward compliance discipline; enterprise SaaS rewards reference accounts; healthcare rewards regulatory + security depth.\n- **Late entry is a structural disadvantage.** Entering after the RFP issued, with no relationship history, drops base rate ~15%. The skill names this, doesn't hide it.\n\n## Anti-patterns\n\n- **Inventing a proof point to fill a GAP.** Hard rule violation. GAPs surface for leadership decision, not for prose-laundering. See `references\u002Frfp_anti_patterns.md`.\n- **Responding to every RFP.** Without a qualified bid \u002F no-bid gate, the team burns capacity on \u003C20% winrate pursuits and loses the 50%+ pursuits to lack of focus. Bain commercial-discipline research.\n- **Generic response with no win-theme.** A proposal that could be sent verbatim by any competitor is decorative. Shipley failure mode #1.\n- **Missing a mandatory disqualifier late.** FedRAMP \u002F HIPAA \u002F ISO 27001 \u002F SOC 2 \u002F on-shore data residency caught on Day 12 of a 14-day response = wasted pursuit. Parser surfaces these on Day 1.\n- **Answering the question YOU wanted asked.** RFP responder discipline: answer what they asked, in their words, in their order. Re-framing belongs in cover letters, not in the compliance matrix.\n- **No compliance matrix.** Every requirement should map to a response section + page number. Evaluators score on a matrix; respondents who don't provide one self-disqualify on traceability.\n- **Late-entry without acknowledging the relationship deficit.** Entering cold against an incumbent with a 3-year relationship and no champion = sub-20% winrate. Pretending otherwise wastes Sales Engineering capacity.\n- **Treating WEIGHTED requirements like MANDATORY.** Score-weighted requirements reward depth on the high-weight items, not uniform mediocrity across all. Shipley capture method.\n\n## Distinct from\n\n- **`business-growth\u002Fcontract-and-proposal-writer`** — free-form narrative proposals where YOU set the structure (executive briefs, capability statements, unsolicited proposals). RFP-responder handles **buyer-dictated structured Q&A** where the buyer set the questions, sections, scoring criteria, and format. Different artifact, different decision logic.\n- **`c-level-advisor\u002Fgeneral-counsel-advisor`** — contract redline and IP\u002Frisk review AFTER award. RFP-responder operates BEFORE award, on the response strategy.\n- **`marketing-skill\u002F*`** — external marketing assets (web copy, content, ASO, SEO, brand voice) for many-to-many audiences. RFP-responder produces a **single-buyer artifact** with deterministic compliance requirements.\n- **`commercial\u002Fdeal-desk`** — per-deal discount routing on a closing opportunity. RFP-responder is pursuit-stage; deal-desk is close-stage.\n- **`commercial\u002Fpricing-strategist`** — pricing-model design for a new product. RFP-responder consumes existing pricing as input to the commercial-terms section.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time before any script runs. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your STRONG \u002F PARTIAL \u002F GAP split on the MANDATORY requirements?\"**\n   Recommended: STRONG ≥ 70% on MANDATORY before bidding. PARTIAL\u002FGAP on any MANDATORY = either close the gap pre-submission or no-bid.\n   Canon: Shipley *Proposal Guide v6* — capture-management discipline, \"Pgw (probability of win) is bounded by your weakest MANDATORY.\"\n\n2. **\"Is there an incumbent, and how strong is their position?\"**\n   Recommended: strong incumbent (3+ years, no displacement event) drops base winrate ~30%. Don't bid without a named displacement trigger.\n   Canon: Forrester B2B-RFP research — incumbents win 70-80% of renewal RFPs absent a named failure event.\n\n3. **\"Did you enter the conversation before or after the RFP issued?\"**\n   Recommended: late-entry (after RFP issued, no prior engagement) drops winrate ~15% and signals the RFP was scoped to someone else's strengths.\n   Canon: Tom Searcy + Henry DeVries *How to Win Big Business* — \"If you didn't help write the RFP, you're column fodder.\"\n\n4. **\"What are your 3-5 win-themes, and does each thread through ≥2 requirements?\"**\n   Recommended: themes that appear in only one requirement are decorative. Themes must ladder up across MANDATORY + WEIGHTED sections.\n   Canon: Shipley *Capture Guide* — win-themes are the buyer-side answer to \"why us\" across the evaluation criteria, not seller-side feature lists.\n\n5. **\"For every claim in the response, can you name the verifiable source?\"**\n   Recommended: every claim → case study \u002F certification \u002F customer reference \u002F technical attestation \u002F benchmark. Unsourced claims = GAPs.\n   Canon: APMP BoK — \"Substantiation: every assertion in a proposal must be backed by evidence the evaluator can independently verify.\"\n\n6. **\"What's the bid \u002F no-bid threshold you committed to BEFORE seeing this RFP?\"**\n   Recommended: pre-committed threshold (e.g., winrate ≥ 25%, STRONG ≥ 70% on MANDATORY, named champion). Post-hoc rationalization is how teams end up bidding 5% pursuits.\n   Canon: Bain RFP-win-rate studies — disciplined bid\u002Fno-bid gates lift win-rate from ~15% to ~35%.\n\n7. **\"What does the buyer's evaluation team actually score on?\"**\n   Recommended: if the RFP discloses scoring criteria, weight your response effort proportionally. If undisclosed, ask. If you can't ask, that itself is a relationship-deficit signal.\n   Canon: Strategic Proposals proposal-management research — evaluators score on the rubric they were given, not on your narrative.\n\nWalk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke `rfp_parser.py` → `response_drafter.py` → `winrate_predictor.py` in sequence. If question 6 lands on \"we don't have a threshold,\" set one now or no-bid.\n","# rfp-responder\n\n## Purpose\n\nHelp Bid Managers, Proposal Leads, and Directors of Sales answer five questions at the response-strategy moment:\n\n1. **What is this RFP actually asking?** (parse sections, tag every requirement MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints)\n2. **What is our true fit?** (proof-point matrix per requirement: STRONG \u002F PARTIAL \u002F GAP, each backed by a verifiable source — case study, certification, customer quote, technical attestation, benchmark)\n3. **What is our win-theme strategy?** (Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets)\n4. **What is our realistic winrate?** (Shipley-derived factor model: fit, incumbent, relationship strength, decision-criteria alignment, late-entry, competitor count, deal size — produces estimate + confidence band)\n5. **Should we bid?** (deterministic verdict: BID \u002F PARTNER-BID \u002F NO-BID with named factors driving the call)\n\nThe skill surfaces GAPs explicitly. Leadership decides whether to close them, partner around them, or no-bid. **It never invents claims.**\n\n## When to use\n\n- A 30+ page RFP \u002F RFI \u002F RFQ has landed with a 7-14 day response deadline\n- A security questionnaire (SIG, CAIQ, custom-buyer) needs structured Q&A — not prose\n- The team is preparing a bid \u002F no-bid review and needs a defensible winrate estimate\n- Sales Engineering has a proof-point library but no system to map proofs to requirements\n- Leadership wants to see fit % (STRONG \u002F PARTIAL \u002F GAP) before committing pursuit budget\n- A late-entry opportunity needs honest assessment of the relationship deficit\n\n**Do not use for:**\n- Free-form proposal narrative authoring → `business-growth\u002Fcontract-and-proposal-writer`\n- Contract redline AFTER award → `c-level-advisor\u002Fgeneral-counsel-advisor`\n- Marketing collateral \u002F category content → `marketing-skill\u002F*`\n- Discount approval on the awarded deal → `commercial\u002Fdeal-desk`\n- Pricing-model design for a new product → `commercial\u002Fpricing-strategist`\n\n## Workflow\n\n### Step 1 — Parse the RFP\n\nDrop the RFP markdown \u002F text into `scripts\u002Frfp_parser.py`. Output: structured JSON listing every requirement, tagged MANDATORY \u002F WEIGHTED \u002F NICE-TO-HAVE based on cue words (must \u002F shall = MANDATORY; should \u002F weighted scoring numbers = WEIGHTED; may \u002F preferred \u002F desired = NICE-TO-HAVE). Captures section structure, scoring criteria if disclosed, deadline, submission format constraints.\n\n```bash\npython scripts\u002Frfp_parser.py --input rfp.md --output json > parsed.json\n```\n\n### Step 2 — Score fit per requirement\n\nFill `assets\u002Frfp_intake_template.md` with your proof-point library (each proof tagged with type + verifiable source + which requirement-tags it covers) and proposed win-themes. Feed parsed RFP + intake into `scripts\u002Fresponse_drafter.py`. Output: proof-point matrix per requirement with STRONG \u002F PARTIAL \u002F GAP, win-theme injection, GAP audit.\n\n```bash\npython scripts\u002Fresponse_drafter.py --input draft_input.json --output markdown > matrix.md\n```\n\n**Hard rule:** GAP requirements are surfaced, never invented around. Leadership reads the GAP audit and decides: close the gap, partner-bid, or no-bid.\n\n### Step 3 — Apply win-theme strategy\n\nShipley method: 3-5 themes that span requirements. Each theme answers \"why us over the incumbent \u002F competitor on the criteria the buyer named.\" `response_drafter.py` shows which themes thread through which requirements — a theme appearing in \u003C2 requirements is decorative, not strategic, and gets flagged.\n\n### Step 4 — Estimate winrate\n\nFeed deal context (fit %, incumbent strength, relationship, decision-criteria alignment, late-entry, competitor count, deal size vs. average) into `scripts\u002Fwinrate_predictor.py`. Output: Shipley-derived estimate 0-100% + confidence band + factor breakdown + BID \u002F PARTNER-BID \u002F NO-BID verdict.\n\n```bash\npython scripts\u002Fwinrate_predictor.py --input deal_context.json --profile enterprise-software --output markdown\n```\n\n**No-bid threshold:** estimate \u003C 20% triggers automatic no-bid recommendation.\n\n### Step 5 — Decide\n\nTake parsed RFP + proof-point matrix + GAP audit + winrate estimate into the go \u002F no-go review. Skill does not commit pursuit budget — leadership does.\n\n## Scripts\n\n- `scripts\u002Frfp_parser.py` — section + requirement extractor (regex + cue-word heuristics, stdlib only)\n- `scripts\u002Fresponse_drafter.py` — proof-point matrix + win-theme injection + GAP audit\n- `scripts\u002Fwinrate_predictor.py` — Shipley-derived factor model + bid\u002Fno-bid verdict, industry-profile-tuned\n\nAll scripts: stdlib only (argparse, json, sys, pathlib, re, collections, statistics). `--help` and `--sample` work on all three.\n\n## References\n\n- `references\u002Fshipley_method_canon.md` — Shipley Proposal Guide v6, Shipley Capture Guide, APMP BoK, Tom Sant, Tom Searcy + Henry DeVries, Strategic Proposals research, Larry Newman\n- `references\u002Frfp_strategy_canon.md` — FAR, GSA, Forrester, Gartner, Bain, McKinsey, B2B International on RFP win-rates and buyer behavior\n- `references\u002Frfp_anti_patterns.md` — Shipley failure modes, APMP cases, Strategic Proposals research, federal loss reviews, MIT Sloan, Bain commercial-discipline, Gartner\n\n## Assumptions\n\n- **The RFP is the ground truth.** If the buyer asked it, answer it — in the order they asked, in the format they specified. Re-organizing for narrative flow is for proposals, not RFPs.\n- **Proof points must be verifiable.** A claim is only as strong as the case study, certification, customer reference, or technical attestation backing it. Unsourced claims become GAPs.\n- **Win-themes are buyer-side, not seller-side.** \"We're the leader in X\" is a marketing claim; \"Your operations team reduces incident MTTR by 60% with the same headcount\" is a win-theme. Shipley canon, not optional.\n- **Winrate estimates are directional.** The model is a discipline tool to force honest pursuit-qualification — not an oracle. Confidence band always wider than the point estimate suggests.\n- **Industry profiles tune base rates** — government RFPs reward compliance discipline; enterprise SaaS rewards reference accounts; healthcare rewards regulatory + security depth.\n- **Late entry is a structural disadvantage.** Entering after the RFP issued, with no relationship history, drops base rate ~15%. The skill names this, doesn't hide it.\n\n## Anti-patterns\n\n- **Inventing a proof point to fill a GAP.** Hard rule violation. GAPs surface for leadership decision, not for prose-laundering. See `references\u002Frfp_anti_patterns.md`.\n- **Responding to every RFP.** Without a qualified bid \u002F no-bid gate, the team burns capacity on \u003C20% winrate pursuits and loses the 50%+ pursuits to lack of focus. Bain commercial-discipline research.\n- **Generic response with no win-theme.** A proposal that could be sent verbatim by any competitor is decorative. Shipley failure mode #1.\n- **Missing a mandatory disqualifier late.** FedRAMP \u002F HIPAA \u002F ISO 27001 \u002F SOC 2 \u002F on-shore data residency caught on Day 12 of a 14-day response = wasted pursuit. Parser surfaces these on Day 1.\n- **Answering the question YOU wanted asked.** RFP responder discipline: answer what they asked, in their words, in their order. Re-framing belongs in cover letters, not in the compliance matrix.\n- **No compliance matrix.** Every requirement should map to a response section + page number. Evaluators score on a matrix; respondents who don't provide one self-disqualify on traceability.\n- **Late-entry without acknowledging the relationship deficit.** Entering cold against an incumbent with a 3-year relationship and no champion = sub-20% winrate. Pretending otherwise wastes Sales Engineering capacity.\n- **Treating WEIGHTED requirements like MANDATORY.** Score-weighted requirements reward depth on the high-weight items, not uniform mediocrity across all. Shipley capture method.\n\n## Distinct from\n\n- **`business-growth\u002Fcontract-and-proposal-writer`** — free-form narrative proposals where YOU set the structure (executive briefs, capability statements, unsolicited proposals). RFP-responder handles **buyer-dictated structured Q&A** where the buyer set the questions, sections, scoring criteria, and format. Different artifact, different decision logic.\n- **`c-level-advisor\u002Fgeneral-counsel-advisor`** — contract redline and IP\u002Frisk review AFTER award. RFP-responder operates BEFORE award, on the response strategy.\n- **`marketing-skill\u002F*`** — external marketing assets (web copy, content, ASO, SEO, brand voice) for many-to-many audiences. RFP-responder produces a **single-buyer artifact** with deterministic compliance requirements.\n- **`commercial\u002Fdeal-desk`** — per-deal discount routing on a closing opportunity. RFP-responder is pursuit-stage; deal-desk is close-stage.\n- **`commercial\u002Fpricing-strategist`** — pricing-model design for a new product. RFP-responder consumes existing pricing as input to the commercial-terms section.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time before any script runs. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your STRONG \u002F PARTIAL \u002F GAP split on the MANDATORY requirements?\"**\n   Recommended: STRONG ≥ 70% on MANDATORY before bidding. PARTIAL\u002FGAP on any MANDATORY = either close the gap pre-submission or no-bid.\n   Canon: Shipley *Proposal Guide v6* — capture-management discipline, \"Pgw (probability of win) is bounded by your weakest MANDATORY.\"\n\n2. **\"Is there an incumbent, and how strong is their position?\"**\n   Recommended: strong incumbent (3+ years, no displacement event) drops base winrate ~30%. Don't bid without a named displacement trigger.\n   Canon: Forrester B2B-RFP research — incumbents win 70-80% of renewal RFPs absent a named failure event.\n\n3. **\"Did you enter the conversation before or after the RFP issued?\"**\n   Recommended: late-entry (after RFP issued, no prior engagement) drops winrate ~15% and signals the RFP was scoped to someone else's strengths.\n   Canon: Tom Searcy + Henry DeVries *How to Win Big Business* — \"If you didn't help write the RFP, you're column fodder.\"\n\n4. **\"What are your 3-5 win-themes, and does each thread through ≥2 requirements?\"**\n   Recommended: themes that appear in only one requirement are decorative. Themes must ladder up across MANDATORY + WEIGHTED sections.\n   Canon: Shipley *Capture Guide* — win-themes are the buyer-side answer to \"why us\" across the evaluation criteria, not seller-side feature lists.\n\n5. **\"For every claim in the response, can you name the verifiable source?\"**\n   Recommended: every claim → case study \u002F certification \u002F customer reference \u002F technical attestation \u002F benchmark. Unsourced claims = GAPs.\n   Canon: APMP BoK — \"Substantiation: every assertion in a proposal must be backed by evidence the evaluator can independently verify.\"\n\n6. **\"What's the bid \u002F no-bid threshold you committed to BEFORE seeing this RFP?\"**\n   Recommended: pre-committed threshold (e.g., winrate ≥ 25%, STRONG ≥ 70% on MANDATORY, named champion). Post-hoc rationalization is how teams end up bidding 5% pursuits.\n   Canon: Bain RFP-win-rate studies — disciplined bid\u002Fno-bid gates lift win-rate from ~15% to ~35%.\n\n7. **\"What does the buyer's evaluation team actually score on?\"**\n   Recommended: if the RFP discloses scoring criteria, weight your response effort proportionally. If undisclosed, ask. If you can't ask, that itself is a relationship-deficit signal.\n   Canon: Strategic Proposals proposal-management research — evaluators score on the rubric they were given, not on your narrative.\n\nWalk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke `rfp_parser.py` → `response_drafter.py` → `winrate_predictor.py` in sequence. If question 6 lands on \"we don't have a threshold,\" set one now or no-bid.\n",{"name":5,"tags":44,"author":46,"context":47,"license":15,"version":48,"description":7,"compatible_tools":49},[45,21,36,35,34,33,32,31,30],"commercial","claude-code-skills","fork","2.8.0",[50,51,52,53,54,55],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Frfp-responder","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill rfp-responder",{"tool":71,"command":72},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill rfp-responder",{"tool":74,"command":75},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill rfp-responder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frfp-responder\u002FSKILL.md",true,[],[80,112,137,164,189,213],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":91,"publishedAt":39},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":39},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[119,120,121,122,96,123,124,125,126,127,128,129,130,131,132,133,134,135,136,108],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":146,"publishedAt":39},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",[147,130,148,149,150,151,152,153,132,154,155,56,156,157,158,159,160,161,162,163],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":39},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[171,172,173,174,175,176,177,178,179,132,180,103,181,182,183,184,185,186,187,188],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":39},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[195],{"categoryNo":144,"categoryName":145,"taxonomyType":89,"taxonomyTypeDesc":90},[197,198,199,200,201,149,176,202,203,204,205,206,130,207,102,208,209,210,211,212],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":39},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[220,221,222,223,224,225,226,227,38,205,228,229,230,231,232,233,104,234,235,188],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","projects","project-management","scanner","conversation","back","project","sprint","cadence"]