Collateral Analyzer

Reads all client-provided collateral (RFP documents, PRDs, org materials, prior proposals, case study notes) and produces a structured brief and gap report. Trigger when the user provides RFP materials, says "analyze the collateral," "start the RFP response," "what do we have to work with," or drops files for an RFP engagement. This skill runs first, always. Nothing downstream is trustworthy without it.

10 stars 3 forksLearning & Education

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add gener8v/gener8v.claude-skills.rfp-response --skill collateral-analyzer
Manual install
git clone --depth 1 https://github.com/gener8v/gener8v.claude-skills.rfp-response.git /tmp/gener8v.claude-skills.rfp-response
mkdir -p ~/.claude/skills
cp -r /tmp/gener8v.claude-skills.rfp-response/rfp-toolkit/collateral-analyzer ~/.claude/skills/collateral-analyzer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## Inputs

- **Client collateral** — any combination of:
  - RFP/RFI document(s)
  - Product Requirements Documents (PRDs)
  - Organization overview documents (about-us pages, capability statements, past performance summaries)
  - Prior proposals or response excerpts
  - Case study notes or drafts
  - Raw notes, emails, or meeting summaries from the capture team
- Files may be `.md`, `.txt`, `.pdf`, or pasted text. Accept whatever is provided.

## Outputs

- **`brief.md`** — structured synthesis of all collateral: who the client is, what they need, how they will evaluate, and how confident we are in each area
- **`gap-report.md`** — per-RFP-section view of what evidence is missing, what is thin, and what questions must be resolved before drafting

---

## Purpose

This skill is the foundation of the pipeline. Every downstream skill — requirements mapping, section drafting, empathy review, compliance validation, assembly — depends on the brief and gap report being honest and thorough. The collateral analyzer does not generate prose for the proposal. It reads, categorizes, extracts, and synthesizes. Its job is to give the drafter a clear picture of what we know, what we can claim, and what we cannot.

## Process

### Step 1: Inventory the Collateral

Read every file the user provides. Categorize each into one of these types:

| Type | What to Look For |
|------|-----------------|
Read the full skill on GitHub

Details

Skill name
collateral-analyzer
Path
rfp-toolkit/collateral-analyzer/SKILL.md
Repo updated
16 April 2026

FAQ

What does the Collateral Analyzer skill do?

Reads all client-provided collateral (RFP documents, PRDs, org materials, prior proposals, case study notes) and produces a structured brief and gap report. Trigger when the user provides RFP materials, says "analyze the collateral," "start the RFP response," "what do we have to work with," or drops files for an RFP engagement. This skill runs first, always. Nothing downstream is trustworthy without it.

How do I install the Collateral Analyzer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add gener8v/gener8v.claude-skills.rfp-response --skill collateral-analyzer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Collateral Analyzer popular?

It lives in gener8v/gener8v.claude-skills.rfp-response, which has 10 GitHub stars and 3 forks.

Related skills

Compliance Validator

10

gener8v/gener8v.claude-skills.rfp-response

Validates every reviewed section against the RFP's explicit requirements. Produces a pass/fail compliance report with remediation notes. Runs after the empathy reviewer because tone fixes can inadvertently remove compliance-critical language. Trigger when the user says "check compliance," "validate the sections," "are we compliant," "run the compliance check," or after the empathy reviewer has produced sections/*-reviewed.md files.

Productivity & Notes

Empathy Reviewer

10

gener8v/gener8v.claude-skills.rfp-response

Reviews each drafted section for tone, voice, and client-centricity. Flags where the proposal sounds like it was written for a generic client rather than this specific one. This is a relationship pass, not a grammar pass. Trigger when the user says "review for tone," "empathy pass," "check the voice," "does this sound right," or after the section drafter has produced sections/*.md files.

Images, Video & Audio

Proposal Assembler

10

gener8v/gener8v.claude-skills.rfp-response

Assembles all reviewed, validated sections into a single proposal-final.md. Inserts front matter, enforces section order, attaches appendices, performs a final compliance pre-flight, and surfaces any unresolved issues. Trigger when the user says "assemble the proposal," "build the final document," "put it together," or after the compliance validator has produced compliance-report.md. Will refuse to assemble if critical compliance failures exist.

Other

Close

10

charlie947/skills-for-everyone

End a good session properly. Banks what the session taught into Claude's memory so the next session starts smarter, finishes every loose end it can, proves the changes actually landed, and hands back only what genuinely needs you. Four phases, in order: LEARN, FIX, PROVE, REPORT. Use when the user says "close", "/close", "close out", "wrap this up", "are we good to close?", "what's still open?", "anything left?", "did we miss anything", "save progress", "bank what we learned", "remember this for next time", "lock in our corrections", or otherwise signals a session is ending. Not for handing wo

Learning & Education

Learn

9

deejay-hub/salesforce-ada-agent-skills

Educate on Salesforce architecture topics with structured, citation-grounded responses. Use when the user wants to understand a concept, pattern, feature, or best practice.

Learning & Education

Oldhand Learn

9

berwinsingh/oldhand

Captures the durable, non-obvious lessons from a task (diagnosis recipes, API and platform quirks, environment traps, failed experiments with their numbers, decisions and their why, rollback points, user corrections) into the project's existing agent instruction file or the host's memory system, each note dated with why and how to apply, and corrects or deletes notes the task proved wrong. Use when the user says "write down what we learned on this task", "save the lessons from this task", "capture this task's lessons for next time", or at the end of the oldhand chain. Not for documenting code

Learning & Education

Browse the most popular Claude skills, all learning & education skills, or write your own with the skills generator.