Claude
Skill
rfp-writer
Respond to RFPs, RFQs, tenders, and cahiers des charges - compliance matrix, requirement mapping, and structured answers. Use for formal procurement responses.
Virus-scanned
Reviewed automatically before listing.
Download
navinspire-ia-navin-navin_skills_rfp-writer-e9c73a3.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/rfp-writer
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git
git clone https://github.com/Navinspire-ia/navin.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
RFP/RFQ Writer
Overview
Tenders are won on compliance first, differentiation second. Miss one mandatory requirement and the best offer is eliminated.
Method
1. Deconstruct the RFP
- Extract every requirement into a compliance matrix:
| # | Requirement | Mandatory? | Our answer | Evidence | Page | - Flag: deadlines, format rules, page limits, required certificates, submission method
- List admin documents needed (registres, attestations, références - critical in DZ/Gulf public tenders)
2. Bid/no-bid check
Score: can we deliver? do we have references? is price competitive? do we know the buyer? - advise honestly.
3. Write the response
- Follow their structure and numbering exactly - evaluators score against a grid
- Answer each requirement explicitly ("Compliant - here's how"), never by omission
- Differentiators woven into answers, not in a separate brochure section
- Reuse vetted content blocks (past responses,
case-study-writeroutputs) - adapted, not pasted - On the Tenders desk,
tenders action=writealready builds a professional dossier in the notice language: cover, contents, letter, executive summary, company, need, approach, vision, functional, technical, methodology, KPIs, RACI/risks, governance, planning, budget, references, compliance matrix. Study that pack first. Do not invent a certificate, price or reference.
4. Review
- Compliance matrix 100% green before polish
- Independent read:
critic-reviewerfor gaps - Format check: page limits, fonts, signatures, annexes order
Workflow tools
Extract requirements from PDFs with pdf-ocr-extractor; produce final docs with docx-generator/pdf-generator; draw architecture / methodology / sequence diagrams with archify; track deadlines with cron reminders; watch new tenders with tender-monitor.
Rules
- Never claim a certification or reference you don't have.
- Deadline math includes submission logistics (physical copies, platforms).
Files (navin)
-
SKILL.md 2.2 KB
--- name: rfp-writer description: Respond to RFPs, RFQs, tenders, and cahiers des charges - compliance matrix, requirement mapping, and structured answers. Use for formal procurement responses. metadata: {"navin":{"emoji":"🏛️","category":"writing"}} --- # RFP/RFQ Writer ## Overview Tenders are won on compliance first, differentiation second. Miss one mandatory requirement and the best offer is eliminated. ## Method ### 1. Deconstruct the RFP - Extract every requirement into a **compliance matrix**: `| # | Requirement | Mandatory? | Our answer | Evidence | Page |` - Flag: deadlines, format rules, page limits, required certificates, submission method - List admin documents needed (registres, attestations, références - critical in DZ/Gulf public tenders) ### 2. Bid/no-bid check Score: can we deliver? do we have references? is price competitive? do we know the buyer? - advise honestly. ### 3. Write the response - Follow *their* structure and numbering exactly - evaluators score against a grid - Answer each requirement explicitly ("Compliant - here's how"), never by omission - Differentiators woven into answers, not in a separate brochure section - Reuse vetted content blocks (past responses, `case-study-writer` outputs) - adapted, not pasted - On the Tenders desk, `tenders action=write` already builds a professional dossier in the **notice language**: cover, contents, letter, executive summary, company, need, approach, vision, functional, technical, methodology, KPIs, RACI/risks, governance, planning, budget, references, compliance matrix. Study that pack first. Do not invent a certificate, price or reference. ### 4. Review - Compliance matrix 100% green before polish - Independent read: `critic-reviewer` for gaps - Format check: page limits, fonts, signatures, annexes order ## Workflow tools Extract requirements from PDFs with `pdf-ocr-extractor`; produce final docs with `docx-generator`/`pdf-generator`; draw architecture / methodology / sequence diagrams with `archify`; track deadlines with `cron` reminders; watch new tenders with `tender-monitor`. ## Rules - Never claim a certification or reference you don't have. - Deadline math includes submission logistics (physical copies, platforms).
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.