Menu

Individual skill

cowork-rfp-response

0upvotes

Turn an RFP and a folder of your past proposals, case studies, and capability docs into a requirement-by-requirement compliance matrix and a drafted response. Flags disqualifiers and unanswerable requirements before you burn a week writing.

cowork-rfp-response/SKILL.md

Read pinned source

Source commit b2267d9171af4f56848d82992381b20b89b44056

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
425
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Cowork RFP Response

Respond to an RFP the way a seasoned proposal manager does: decompose every requirement first, decide bid/no-bid honestly, reuse the best prior language, and never claim a capability the source documents do not support. Inputs: the RFP document and a folder of company material (past proposals, case studies, bios, certifications, pricing sheets).

## Workflow

1. **Shred the RFP.** Extract every numbered and implied requirement into a matrix: ID, requirement text (verbatim), type (mandatory/scored/informational), section owner, and any disqualifier ("must have X certification", "minimum N years"). Extract the logistics separately: due date, format, page limits, submission method, Q&A deadline, evaluation criteria and weights.
2. **Bid/no-bid check.** Before drafting anything, report disqualifiers you cannot document from the company folder and requirements with weak evidence. Ask whether to proceed. This is the most valuable five minutes of the skill.
3. **Mine the folder.** For each requirement, find the strongest supporting material: prior proposal sections, case studies with named results, team bios, certifications. Record source file and section in the matrix. Mark each requirement `STRONG` (direct evidence), `PARTIAL` (adjacent evidence, needs framing), or `GAP` (nothing found).
4. **Draft.** Write the response following the RFP's mandated structure exactly. For `STRONG` items, adapt the best prior language to this client's context. For `PARTIAL`, draft honest framing and flag it for review. For `GAP`, insert a clearly marked `[GAP: needs input -- suggested approach]` block rather than fiction.
5. **Compliance pass.** Verify every mandatory requirement is addressed where the RFP says it must be, page/format limits hold, and required attachments are listed. Output `compliance-matrix.md` (the full matrix with response locations) and `rfp-response-draft.md`.
6. **Executive summary last.** Write it after the body, leading with the client's stated problem in their own vocabulary and the 2-3 discriminators the evidence actually supports.

## Rules
Back to top