Quotation Kit

Problem

Enterprise quotation drafts often require repeated confirmation of customer name, product, bandwidth, contract term, one-time fees, and contacts. Manual HTML quoting can miss fields, mix calculation rules, or use the wrong fixed contract term. This skill turns quotation drafting into structured follow-up questions, using ask_followup_question to collect each item and reduce skipped or inconsistent inputs.

How It Works

• Information gathering: It confirms unit name, product name, bandwidth/spec, unit price, quantity, contract term, one-time fees, AZ endpoints, use case, and contact roles. Ambiguous names such as restaurants are clarified first to separate hotel/guest-house from retail food shop scenarios.
• Scenario matching and pricing: It maps unit keywords to office building, individual shop, or hotel scenarios and suggests preset packages. If no unit price is provided, it can look up references/pricing.md by urban or township keywords and ask the user to confirm the source.
• Calculation and output: It computes monthly fee = unit price × quantity, annual fee = monthly fee × 12, and total contract fee = annual fee × contract years + one-time fees, with thousand separators and Chinese capital amounts. The generated HTML follows assets/template.html, writes quotation_.html, and opens a local http.server preview.

Boundaries

It is best for enterprise customer quotation drafts, especially data lines, internet lines, WiFi coverage, and camera packages. Users should maintain references/pricing.md and the product knowledge base themselves. Packages fixed to a 3-year contract are auto-filled and not asked again. Contacts, addresses, and dates may remain blank for manual completion. If ask_followup_question is unavailable, the designed step-by-step flow cannot run.