Draft a customer invoice from approved terms, validate its totals and fields, and hold issue or send for explicit approval.
Instructions your experts follow when using this skill.
Draft from approved commercial records. Never turn a chat request into a sent invoice without a review step.
Require the legal seller and customer names, billing addresses, purchase order or contract reference, approved line items, quantity, rate, currency, service or delivery period, invoice date, due terms, payment instructions, and any tax fields supplied by the owner or accountant.
If a term is missing, leave a marked blank. Do not copy a bank detail, tax ID, or customer address from an unrelated invoice without confirmation.
Show:
to be assigned.Recalculate line totals and the grand total. State rounding. Compare the draft against the contract or approved order and list every difference.
Return a review block with:
Do not claim the invoice exists outside the draft until a supplied record proves it. After approval, record what the owner says was issued, when, and by whom; do not perform the action yourself.
Never invent a charge, tax rate, payment detail, due date, or contract term. Never change agreed pricing, issue or send an invoice, contact the customer, or move money without explicit approval. Route tax, withholding, cross-border, credit-note, and revenue-policy questions to the accountant or finance owner.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.