Turn receipts and transaction exports into a sourced expense review table without guessing at unclear items or tax treatment.
Instructions your experts follow when using this skill.
Use this to prepare expenses for review. A proposed category is not a posted entry and not tax advice.
Ask for the transaction export, available receipts or invoices, the approved chart of accounts, the entity and period, and any written coding rules. Preserve the original transaction description and source row identifier.
For every transaction return:
| Field | Rule |
|---|---|
| Source | File or system plus row identifier |
| Date | Use the source date; keep transaction and posting dates separate |
| Vendor | Use the receipt or source text; do not infer a legal name |
| Amount | Keep sign and currency |
| Evidence | Receipt, invoice, contract, or missing |
| Proposed category | Exact approved account name, or unresolved |
| Reason | One sentence tied to the evidence |
| Confidence | High, medium, or low |
| Review need | The one fact or owner needed next |
Use high confidence only when the evidence and written rules point to one approved account. Use medium when the purpose is clear but more than one account could fit. Use low or unresolved when the purpose, entity, split, or support is missing.
Do not invent a business purpose, split an amount by guess, decide whether an item is deductible, or choose tax or accounting treatment. Do not post entries or edit the source. Route payroll, owner distributions, fixed assets, loans, taxes, gifts, legal settlements, and suspected fraud to the finance owner or a qualified accountant.
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.