← VoltformerCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Voltformer
Snapshot Sep 30, 2026 · 23:11 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "voltformer-rfq-preparation",
"description": "Prepare a complete Voltformer electrical-equipment quotation request from member profiles, projects, catalog products, and specification PDFs. Use for RFQ drafting, validation, attachment preparation, or explicitly confirmed submission.",
"included_files": [],
"skill_md_contents": "---\nname: voltformer-rfq-preparation\ndescription: Prepare a complete Voltformer electrical-equipment quotation request from member profiles, projects, catalog products, and specification PDFs. Use for RFQ drafting, validation, attachment preparation, or explicitly confirmed submission.\n---\n\n# Voltformer RFQ preparation\n\nPrepare an accurate quotation request while keeping drafting separate from irreversible submission.\n\n## Workflow\n\n1. Require a connected member before accessing private data. Read available company profiles and projects only when they help fulfill the request.\n2. Resolve every requested item to a known Voltformer catalog product and retrieve its details. Do not submit free-text products as if they were catalog matches.\n3. Ask for missing operational details, quantity, delivery destination, requested timing, site conditions, standards, and whether a technical-specification PDF exists. Omit genuinely unknown optional fields.\n4. For a PDF available in chat, use `uploadSpecificationInline` within its size limit. For larger files, use `createSpecificationUploadUrl`, have the file uploaded, then call `finalizeSpecificationUpload`.\n5. Show a final summary containing customer/profile, project, products, quantities, delivery information, specification attachment, assumptions, and unresolved details.\n6. Ask for explicit confirmation to submit that exact summary. Call `submitRfqQuoteRequest` only after confirmation, then return the durable request reference and optionally verify it with `listRfqs`.\n\n## Invariants\n\n- Never treat discussion, drafting, file upload, or a prior confirmation for different content as permission to submit.\n- An RFQ requests a quotation; it is not a purchase order, payment, contract, price guarantee, or inventory reservation.\n- Use business tax identifiers only when necessary for the quotation; never ask for personal government IDs, credentials, payment data, or authentication codes.\n- Do not expose another member's profiles, projects, files, or RFQs.\n\n"
}SHA-256: f5375b644f696983beef18a95d91ab1e604bda5f8b3b2f043970e64286bf37d8