supplier-rfq
Skill0 starsChanged 47 days agoMITView on GitHub
Build an XLSX supplier request for quotation with reference images embedded beside their items, quantities and supplier response columns. Use for preparing supplier-facing RFQs from confirmed requirements.
In this repository8 other files it gives its agents.
- freight-estimatorSkill
- invoice-builderSkill
- landed-costSkill
- multi-quoteSkill
- quote-auditSkill
- translate-rfqSkill
- whatsapp-rfqSkill
- xlsx-editSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run python scripts/build_supplier_rfq.py INPUT.json --output NEW.xlsx.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Supplier RFQ
If the request identifies a WhatsApp customer or conversation, first use the sibling whatsapp-rfq skill to fetch scoped live messages and attachments. Do not ask the user to copy chats or manually reconstruct items. Use its reviewed supplier-rfq.json; unresolved and withdrawn lines remain outside the generated table. Both skills must be installed for this route.
- Confirm the model/year, part identity, required quantity and reference-image meaning. A picture is not proof of fitment. Preserve the source description separately.
- Prepare JSON with
rfq_no, ISOdate, optionalvehicle/instructions, anditems(1–200). Each item acceptsdescription,source_text,part_no, positivequantity, optionalphotoandnotes. Unknown fields fail. - Run
python scripts/build_supplier_rfq.py INPUT.json --output NEW.xlsx. Photo paths resolve relative to the JSON file.openpyxland Pillow are required. - Open the output, verify each image is on the correct row, and review the quantities and reference notes. Blank Quote A / Quote B / Lead Time fields are for the supplier to fill; specify the currency and quality labels in the instructions.
Pictures are converted to RGB PNG thumbnails without original EXIF/GPS metadata. This does not remove names or sensitive content visibly printed in an image: inspect the actual pixels. Text beginning with = remains literal text. Existing files are never overwritten. No customer-contact fields or fixed company defaults are added; review user-supplied text before sharing. The script creates a file and never contacts a supplier.
Repository example: examples/supplier-rfq.json. Preview: docs/supplier-rfq-preview.png.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

