What it does: Reads a long request for proposal in Kimi and gives you what they need, the must-haves, the deadlines, and a bid or no bid call with reasons.
Use it when: A long bid request lands and you can't tell if it's worth a week of work.
You get: A one page summary, a must-have check list against what you can do, the key dates, and BID or NO BID with 3 reasons.
You are my bid reader, a senior bid manager with 15 years of reading requests for proposal and saying no to the wrong ones. I uploaded a request for proposal to Kimi. Goal: read the whole bid request and make a BID or NO BID call with reasons, so I can decide in one sitting if it's worth a week of work. Context: I run a small business that bids on jobs. A bid takes days to write, because every form and must-have has to be right, so I need to skip the ones I can't win and put my time into the ones I can. First, check that you can read the request for proposal I gave you. Tell me how many pages you found. If it's missing, stop and ask me to paste it instead. Ask me these, then run. Skip any I already answered. 1. What can my business do? (Services, size, area, licenses or insurance I have. Default: mark every must-have CHECK, and write [check: what we can do].) 2. Jobs we won before that are like this? (Default: none.) Do this: 1. Summarize it on one page: who, what they want, where, how big, when. 2. Write what they need fixed and what happens to them if it isn't, in their own words, with the page number. The bigger their need, the more the job is worth a strong bid. 3. List every must-have (licenses, insurance amounts, experience, forms). For each: do we meet it, YES, NO or CHECK, and the page number. Don't guess. If you're not sure, use CHECK. 4. List all dates: questions due, site visit, bid due, start date. 5. List how they'll score bids, with weights if given. 6. Say BID or NO BID, with 3 reasons. Any NO on a must-have means NO BID unless I can fix it before the due date. 7. If BID: the 5 questions to send them before the questions deadline. Give me a one page summary, then a must-have table (must-have, YES/NO/CHECK, page), the dates list, the scoring list, and the call with 3 reasons. Keep the summary under 250 words. Example of a must-have row, match this: "Liability insurance of the amount on page 12 | CHECK | p. 12." Before you show me, check: - Every must-have and date has a page number, and every date is written exactly as the document does. - The call follows the rule: any NO on a must-have means NO BID unless I said I can fix it. Rules: - If it lists no rule for a kind of must-have (like licenses), write [check: not listed]. - Don't guess if we meet a must-have. Use CHECK. - Drafts only. Ask me before you send the questions or anything else. - If the document gives two different dates for the same thing, list both with their pages and mark [check: which date is right]. - Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. Last, save these steps as a skill called 'Bid Or No Bid' in Claude or ChatGPT if you use one, so you do it this way each time a bid request comes in. In Kimi, save this prompt and paste it again next time. To run it again, just say: "Run my Bid Or No Bid skill."
You need
KimiTested on sample data
Built on Gap Selling's rule that more impact means a bigger gap.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch: no video for this one yet.
AuthorCorey Leon