new-quotation
About
The new-quotation skill generates branded sales quotations by collecting client details and populating Sentient.io's template, then automatically stores the document in the correct Work Day Google Drive folder. Use it when sales teams need a pricing proposal or refreshed quote that requires proper commercial formatting and filing. It ensures quotations meet company standards and are archived in the appropriate workflow hierarchy.
Quick Install
Claude Code
Recommended/plugin add https://github.com/christopheryeo/claude-skillsgit clone https://github.com/christopheryeo/claude-skills.git ~/.claude/skills/new-quotationCopy and paste this command in Claude Code to install this skill
Documentation
New Quotation Skill
Create production-ready sales quotations that adhere to Sentient.io's commercial standards and automatically land in the appropriate Work Day folder for record keeping.
When to Use
- A user requests a "new quotation", "customer quote", or pricing proposal for a prospect
- Sales or delivery teams need a refreshed quotation aligned to the Sentient template
- A quotation must be stored in the SNMG18 Working Docs hierarchy alongside other daily files
Required Inputs
Collect and confirm the following details before drafting the quotation:
- Client company name and primary contact details (name, role, email, phone)
- Opportunity or engagement name, objectives, and scope summary
- Proposed deliverables, milestones, and owners
- Pricing line items, quantities, unit prices, taxes, and payment terms
- Commercial assumptions, dependencies, and quotation validity period
- Requested delivery or kickoff timeline
- Target work day (defaults to today) for filing the quotation
If any information is missing, ask the user for clarification before proceeding.
References & Assets
- Load
templates/sentient-quotation-template.mdto follow Sentient.io's structure, section ordering, and branding cues. - For tone and visual consistency, optionally consult the
sentient-brand-guidelinesskill. - Use the
work-dayskill to prepare the destination folder structure in Google Drive.
Workflow
1. Confirm Scope & Inputs
- Paraphrase the request to ensure alignment on the opportunity and deliverables.
- Capture all required inputs in a structured checklist.
- Highlight any gaps or assumptions and request confirmation.
2. Prepare Work Day Folder
- Determine the work day date supplied by the user (or default to today).
- Invoke the work-day skill to ensure the
YYYY-MM Work/YYYY-MM-DDfolder exists underSNMG00 Management/SNMG18 Working Docs. - Record the target folder link or ID for later use.
3. Draft the Quotation
- Open the Sentient Quotation template file (
templates/sentient-quotation-template.md). - Replace placeholder tokens (e.g.,
{{client_company}},{{total_amount}}) with the confirmed inputs. - Maintain Sentient.io's professional, audit-ready tone:
- Use confident yet consultative language.
- Keep executive summary to ≤120 words.
- Align currency and tax references with the user's region.
- Ensure pricing tables total correctly and that taxes/fees are explicit.
- Include acceptance table with client and Sentient signatories.
4. Create Google Doc Deliverable
- Generate a document title using the pattern
Quotation - <Client> - <Engagement> - <YYYYMMDD>. - Use Zapier's Google Docs integration to create a document from plain text:
- Preferred action:
Zapier:google_docs_create_document_from_text(or equivalent) with the assembled markdown converted to clean doc text. - Store the document temporarily in My Drive.
- Preferred action:
- After creation, move the document into the prepared Work Day folder using Google Drive integration (
Zapier:google_drive_move_fileor create-in-folder option). - Set sharing to company-internal (view access) unless user specifies otherwise.
5. Deliver Summary Back to User
Provide a confirmation message that includes:
- Quotation title and Google Drive link
- Target work day folder path
- Summary of major sections (objectives, deliverables, total investment, validity)
- Any follow-up actions or outstanding assumptions
Quality Checklist
Before responding to the user, verify that:
- All template placeholders have been replaced with real values or removed if not applicable
- Pricing totals sum correctly and match the described payment terms
- Assumptions and validity period are explicitly stated
- Document lives in the correct Work Day folder and shares appropriately
- Final response includes link, folder path, and concise recap
Error Handling
- If the work-day skill cannot find/create the target folder, inform the user and pause until resolved.
- If Google Docs creation fails, supply the completed quotation content in-chat and note manual upload is required.
- If required inputs are missing after reasonable clarification attempts, summarize outstanding items instead of proceeding.
Packaging Notes
- Store this skill definition at
new-quotation/skill.md. - Include the template file within
new-quotation/templates/when packaging for deployment. - Update repository README or catalog as needed when promoting this skill to production.
GitHub Repository
Related Skills
llamaindex
MetaLlamaIndex is a data framework for building RAG-powered LLM applications, specializing in document ingestion, indexing, and querying. It provides key features like vector indices, query engines, and agents, and supports over 300 data connectors. Use it for document Q&A, chatbots, and knowledge retrieval when building data-centric applications.
canvas-design
MetaThe canvas-design skill generates original visual art in PNG and PDF formats for creating posters, designs, and other static artwork. It operates through a two-step process: first creating a design philosophy document, then visually expressing it on a canvas. The skill focuses on original compositions using form, color, and space while avoiding copyright infringement by never copying existing artists' work.
go-test
MetaThe go-test skill provides expertise in Go's standard testing package and best practices. It helps developers implement table-driven tests, subtests, benchmarks, and coverage strategies while following Go conventions. Use it when writing test files, creating mocks, detecting race conditions, or organizing integration tests in Go projects.
business-rule-documentation
MetaThis skill provides standardized templates for systematically documenting business logic and domain knowledge following Domain-Driven Design principles. It helps developers capture business rules, process flows, decision trees, and terminology glossaries to maintain consistency between requirements and implementation. Use it when documenting domain models, creating business rule repositories, or bridging communication between business and technical teams.
