Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
Instructions your experts follow when using this skill.
Use this to prepare a receivables review and message drafts. The owner approves all customer contact.
For each open invoice, collect the invoice record, customer, currency, issued
date, due date, original amount, credits, payments, open balance, last contact,
dispute status, and account owner. Check payment records through the stated
cutoff time. If the due date or balance cannot be proved, mark the item status unconfirmed rather than overdue.
Calculate days past due from the supplied due date and cutoff date. Keep part-payments, credits, disputes, and promised payment dates visible.
Group items as:
Within each group, sort by age and open balance, then note any named customer or contract rule that changes the handling. Do not invent a credit policy.
Each draft should state the invoice number, issue and due dates, open balance, currency, and the requested next step. Keep the tone calm. Ask whether payment has been made or whether a record is missing. For a dispute, acknowledge the stated issue and route it to the owner; do not argue the contract.
Prepare a contact log row with draft stage, evidence cutoff, owner, approval state, and next review date. Drafts must not claim a late fee, service stop, collection action, or legal consequence unless an approved policy and owner instruction support it.
Never send a message, call a customer, apply a fee, stop service, change an invoice, or threaten collection. Never expose another customer's data. Route disputes, hardship, insolvency, legal threats, sanctions, and material customer risk to the finance owner or counsel.
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.