cowork-rfp-response — Claude Code skill: what it does, how to install
cowork-rfp-response — a skill for Claude Code that shreds RFP documents and maps requirements against company archives. It flags unanswerable criteria and disqualifiers before drafting starts.
MIT 112 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a claude-codeWhat cowork-rfp-response does
The skill parses proposal requirements into a compliance matrix and drafts responses based on past proposals, case studies, and capability documents. It maintains strict fidelity to existing files.
Every requirement gets tagged as STRONG, PARTIAL, or GAP. Inventing metrics, certifications, or past client references is blocked; unverified items receive explicit gap markers for manual review.
The process generates compliance-matrix.md, rfp-response-draft.md, and a questions-to-submit.md list for client clarifications. Execution requires an RFP file and a folder containing company source files like case studies, bios, certifications, and past proposals.
What it helps with
- extract mandatory requirements and deadlines from an RFP file
- run a bid/no-bid check before writing the proposal
- build a
compliance-matrix.mdlinked to company evidence - draft client Q&A inquiries into
questions-to-submit.md
Example prompts for the agent
- Shred
rfp-requirements.pdf - Should we bid on
rfp.docxusing docs inpast-bids/? - Full response with
company-materials/forclient-rfp.pdf
How to install cowork-rfp-response
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-rfp-response/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-rfp-response/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a codex2Manually: put the files in place
.agents/skills/cowork-rfp-response/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a cursor2Manually: put the files in place
.cursor/skills/cowork-rfp-response/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-rfp-response2Manually: put the files in place
.github/skills/cowork-rfp-response/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-rfp-responseManually: put the files in place
.devin/skills/cowork-rfp-response/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-rfp-response
How to install cowork-rfp-response in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-rfp-response -a claude-code. Alternatively, place the skill file directly at ~/.claude/skills/cowork-rfp-response/SKILL.md.
What does cowork-rfp-response do?
It breaks down RFPs, audits qualification evidence against past company materials, and generates proposal drafts alongside compliance matrices.
What is required to run cowork-rfp-response?
It requires the RFP document and a folder with company files such as previous proposals, certifications, staff bios, and case studies.
Source text
SKILL.md · MIT
---
name: cowork-rfp-response
description: 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.
tools: Read, Glob, Grep, Write, Bash, WebSearch
model: inherit
---
# 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
- Never invent capabilities, clients, metrics, or certifications. Every claim traces to a source file; `GAP` blocks are the honest alternative.
- Use the client's terminology from the RFP, not internal jargon. Evaluators score against their own words.
- Answer the requirement asked, not the adjacent one you have better material for -- then add the better material.
- Respect page limits from the first draft; cutting 40% at the end butchers the good sections.
- Boilerplate is a starting point, not a deliverable. Any reused paragraph must name this client and this context or it gets rewritten.
- Track questions for the Q&A window: ambiguous requirements go in a `questions-to-submit.md` list, drafted in submission-ready form.
## Quick Commands
- "Shred [RFP file]" -- requirements matrix and logistics only
- "Should we bid?" -- steps 1-3, the honest gap report
- "Full response with [folder]" -- complete workflow
- "Compliance check my draft" -- step 5 against an existing draft
© OneWave-AI · MIT · OneWave-AI/claude-skills