Prompt Library

Read sap-ledger-export.xlsx and bank-statement.xlsx.
Match by Transaction_Reference. Flag: posting date differences > 2 business days, amount mismatches > 0.01 (decimal shift pattern), entries in bank missing from SAP, duplicate postings.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Use EUR formatting. Separate suspense account items into their own tab.

Read scheme-report.xlsx and internal-tracker.xlsx.
Match by ARN. Flag: amount mismatches > 100, status conflicts between scheme decision and internal tracker, currency mismatches, approaching deadlines.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Highlight any case where scheme and tracker disagree on outcome.

Read screening-export.xlsx and internal-notes.xlsx.
Match by Alert_ID. Flag: disposition disagreements, high-risk geography alerts with low similarity scores, alerts missing internal review.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Escalate any alert where geography risk overrides low similarity score.

Read country-performance.xlsx and central-report.xlsx.
Match by Country_Code and Metric_Name. Flag: value differences > 5%, metrics present in local but missing from central, date range misalignments between sources.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Group discrepancies by country. Highlight any metric where local reports a higher number than central.

Read ticket-volumes.xlsx and staffing-levels.xlsx.
Match by date. Flag: SLA breaches, understaffed days, overstaffed days, Monday volume spikes.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Highlight any day where ticket-to-agent ratio exceeds 15:1.

Read snowflake-output.xlsx and tableau-totals.xlsx.
Match by Report_Name and Date. Flag: row count differences, sum mismatches > 0.01, reports present in pipeline but missing from dashboard, stale dashboards not refreshed in > 24 hours.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Note any discrepancy that could indicate a broken DBT model or failed Airbyte sync.

Read bank-statement.xlsx and internal-ledger.xlsx.
Match by Reference_Number. Flag: amount differences > 500, timing gaps > 3 days, unreconciled items.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Use EUR currency formatting. Highlight decimal shift patterns.

Read sardine-alerts.xlsx and jira-dispositions.xlsx.
Match by Alert_ID. Flag: alerts in fraud monitoring tool with no Jira case, disposition mismatches (e.g. fraud monitoring tool says high-severity but Jira closed as false positive), cases open > 48 hours without disposition.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Flag any merchant appearing in 3+ unresolved alerts — potential BIN attack or velocity spike.

Read pipeline-deals.xlsx and crm-records.xlsx.
Match by Deal_ID. Flag: value discrepancies, deals marked Closed Won in pipeline but Stale in CRM, name mismatches that might be the same company.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Calculate total pipeline inflation vs reality.

Read okta-users.xlsx and hibob-directory.xlsx.
Match by Employee_ID. Flag: active HiBob employees missing Okta accounts, departed employees still active in Okta, group assignment mismatches vs role, MFA not enabled.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Highlight any departed employee with Okta access still active — security risk.

Read contract-tracker.xlsx and docusign-export.xlsx.
Match by Contract_ID. Flag: contracts marked Executed in tracker but still Pending in DocuSign, agreements past signature deadline, contracts in DocuSign with no tracker entry.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Separate NDAs from commercial agreements. Flag any contract > 30 days without signature.

Read zuper-dispatch.xlsx and courier-confirmations.xlsx.
Match by Order_ID. Flag: dispatched but unconfirmed deliveries > 3 days, delivery date mismatches, terminals dispatched to wrong address, failed deliveries not rebooked.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Group by country. Flag any terminal with 2+ failed delivery attempts for escalation.

Read campaign-tracker.xlsx and braze-performance.xlsx.
Match by Campaign_ID. Flag: campaigns in tracker not found in Braze, send count discrepancies > 10%, campaigns marked Live in tracker but Paused in Braze, missing UTM parameters.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Break out by channel (email, push, in-app, SMS). Highlight campaigns with 0 sends.

Read application-tracker.xlsx and cdd-status.xlsx.
Match by Application_ID. Flag: applications approved in CDD but blocked in operations, stuck applications > 14 days, missing CDD records.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Flag the top 5 longest-waiting applications.

Read workato-bot-logs.xlsx and slack-request-outcomes.xlsx.
Match by Request_ID. Flag: bot executions that failed silently (no Slack confirmation), requests completed in Slack but no workflow automation platform log, recipe errors requiring manual reprocessing.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Group failures by workflow automation platform recipe name. Flag recipes with > 5% failure rate.

Read partner-claims.xlsx and internal-commissions.xlsx.
Match by Partner_ID and Reporting_Week. Flag: amount differences > 1%, merchants claimed by partner but not in internal records, clawback-eligible transactions missing from claims, duplicate payments across countries.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Exclude eCommerce services per commission model rules. Flag any duplicate ISA across multiple countries.

Read hibob-export.xlsx and opsgenie-schedule.xlsx.
Match by Employee_ID and date. Flag: hours differences (scheduled vs logged may be incident callouts, not errors), missing entries in either source.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Distinguish scheduled overtime from unscheduled incident callouts.

Read activation-tracker.xlsx and transaction-records.xlsx.
Match by Merchant_ID. Flag: merchants marked Activated but with zero transactions, merchants transacting but not marked Activated, activation date vs first transaction date gap > 7 days.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Segment by product type (POS vs eCommerce). Flag merchants onboarded > 30 days ago with no first transaction.

Read sprint-plan.xlsx and jira-sprint-report.xlsx.
Match by Ticket_ID. Flag: tickets committed but not started, scope changes (tickets added mid-sprint), story point mismatches between plan and Jira, tickets marked Done in plan but still In Progress in Jira.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Calculate planned vs actual velocity. Flag any ticket reassigned mid-sprint.

Read tier2-escalations.xlsx and resolution-records.xlsx.
Match by Ticket_ID. Flag: escalations with no resolution record, resolution times > SLA, tickets resolved in Tier 2 but still open in Zendesk, duplicate escalations for the same merchant issue.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Group by escalation category. Flag recurring merchant issues (same Merchant_ID appearing 3+ times).

Read cancellation-requests.xlsx and save-outcomes.xlsx.
Match by Merchant_ID. Flag: cancellations with no save attempt, merchants marked Saved but still showing as Cancelled, repricing offers made but not applied, outcome recorded but no call log.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Exclude business-closure cancellations (handled by CR). Calculate save rate by reason code.

Read risk-model-scores.xlsx and merchant-reviews.xlsx.
Match by Merchant_ID. Flag: high-risk scores with no review scheduled, review outcome disagrees with model score (e.g. model says high-risk but review cleared), merchants exceeding chargeback thresholds without restriction, reviews overdue > 30 days.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Flag any merchant with MOTO or manual-entry ratios above guardrail thresholds.

Read scheme-fee-statement.xlsx and internal-fee-calc.xlsx.
Match by Merchant_ID and Fee_Type. Flag: amount differences > 0.50, fee categories billed by scheme but not in internal model, interchange rate mismatches, MCC-driven fee discrepancies.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Separate by scheme (Visa, Mastercard, AMEX). Total the revenue leakage from unmatched fees.

Read sweep-records.xlsx and bank-balances.xlsx.
Match by Sweep_Date and Bank_Account. Flag: sweep amounts not reflected in bank balance, timing differences > 1 business day, partner bank A vs partner bank B split deviating from 80/20 target, balance corrections not reconciled.
Produce a reconciliation workbook (.xlsx) with matched, discrepancy, and summary sheets.
Calculate net safeguarding position per bank. Flag any day where sweep total and bank movement differ by > 1000.

I need a Monday briefing for the Accounting team.
Pull from Jira: all open reconciliation tasks and financial close items for this period.
Pull from Confluence: the current month-end close checklist and any updated accounting procedures.
Search Glean: recent announcements from Treasury or Compliance that affect the close.
Produce a Word document (.docx) with:
- Outstanding reconciliation tasks by type (bank, safeguarding, merchant balance)
- Close checklist items completed vs remaining with owners
- Queries pending from Treasury, Security, or Compliance
- Recommended priorities for this week to stay on track
Keep to 2 pages.

Pull all open chargeback cases from Jira with status In Progress or Pending.
Check Confluence for the latest scheme deadline reference page.
Produce a Word document (.docx) briefing with:
- Cases approaching deadline (< 7 days remaining)
- Cases by scheme (Visa, Mastercard, AMEX) with deadline dates
- Any scheme rule changes from recent Confluence updates
Sort by urgency. Keep to 2 pages.

I need a Monday briefing for the Customer Monitoring Team.
Pull from Jira: open CDD cases, EDD investigations due this week, and periodic refresh escalations.
Pull from Confluence: updated screening procedures and any regulatory guidance changes.
Search Glean: sanctions screening tool or fraud monitoring tool alert volume trends and MLRO communications from the past week.
Produce a Word document (.docx) with:
- Alert backlog size and triage status (open, in review, pending escalation)
- EDD cases due within 7 days with trigger type and merchant risk level
- Periodic refresh pipeline by escalation stage (email, SMS, outbound, final-stage follow-up)
- Regulatory or screening tool changes requiring team action
Keep to 2 pages.

I need a Monday briefing for Country Operations leadership.
Pull from Jira: country-level operational issues, merchant escalations, and open action items across all markets.
Pull from Confluence: market-specific runbooks and any updated local compliance requirements.
Search Glean: recent decisions or announcements affecting specific countries (GB, ES, IT, PT, CZ, HU, IS).
Produce a Word document (.docx) with:
- Open escalations by country with status and owner
- Local compliance or regulatory deadlines approaching this month
- Commission or deal approvals pending governance sign-off
- Cross-country patterns or shared issues worth discussing at the next leaders call
Keep to 2 pages.

Pull all tickets created over the weekend from Jira (Saturday-Sunday).
Search Glean for any related known issues or announcements.
Check Confluence for updated runbooks matching the top ticket categories.
Produce a Word document (.docx) with:
- Weekend ticket count by category
- Escalations requiring immediate attention
- Links to relevant runbooks
- Repeat-issue patterns (3+ tickets for same root cause)

I need a Monday briefing for the Data and Analytics team.
Pull from Jira: open ad-hoc data requests, pipeline incidents, and Tableau migration tickets.
Pull from Confluence: Snowflake Dashboard deprecation timeline and DBT model change log.
Search Glean: data-related requests or escalations posted in Slack channels over the past week.
Produce a Word document (.docx) with:
- Ad-hoc request queue ranked by business priority and estimated complexity
- Pipeline incidents from the past week with resolution status
- Tableau migration progress vs the June 2026 deadline
- Commission data or reporting changes flagged by Finance or Partnerships
Keep to 2 pages.

Pull open reconciliation tickets from Jira for this month.
Search Confluence for month-end close checklist.
Search Glean for any finance announcements or policy changes.
Produce a Word document (.docx) with:
- Open items blocking month-end close
- Reconciliation status by account type
- Outstanding approvals needed
- Key dates and deadlines this week

I need a Monday briefing for the Fraud team.
Pull from Jira: open monitoring cases, investigation queue size, and any merchants flagged for payout blocks last week.
Pull from Confluence: updated fraud rule typologies and any new BIN attack or velocity spike patterns documented.
Search Glean: recent fraud monitoring tool migration updates and chargeback ratio alerts from the past week.
Produce a Word document (.docx) with:
- Investigation queue by severity and detection mode (real-time, near real-time, batch)
- Merchants approaching Visa VAMP or Mastercard MATCH thresholds
- False positive rate trends and snooze list changes
- Tool migration status (Jira to fraud monitoring tool) and any workflow impacts this week
Keep to 2 pages.

I need a Monday briefing for the Inside Sales team.
Pull from Jira: CDD status on deals handed off to onboarding and any blocked merchant applications.
Pull from Confluence: updated sales playbooks and pricing adherence guidelines.
Search Glean: HubSpot pipeline changes, new inbound leads, and deal card updates from the past week.
Produce a Word document (.docx) with:
- Pipeline summary by stage with stale deals flagged (no update > 7 days)
- CDD handoff status: deals cleared, deals pending, deals blocked
- New leads received over the weekend requiring assignment
- Pricing dashboard highlights and any adherence issues to discuss
Keep to 2 pages.

I need a Monday briefing for the IT Helpdesk team.
Pull from Jira: open service desk tickets by category (access requests, MFA resets, hardware, software licences) and SLA status.
Pull from Confluence: known issues, scheduled maintenance windows, and Okta configuration changes.
Search Glean: new joiner start dates from HiBob and any IT-related escalations posted in Slack.
Produce a Word document (.docx) with:
- Ticket queue by category with count and oldest unresolved
- New joiner provisioning due this week (names, departments, required tools)
- Upcoming maintenance windows or system changes affecting users
- Recurring ticket patterns that could be addressed with self-service documentation
Keep to 2 pages.

I need a Monday briefing for the Legal team.
Pull from Jira: open contract review requests, NDA tickets, GDPR requests, and law enforcement responses with deadlines.
Pull from Confluence: updated contract templates, regulatory submission tracker, and RoPA status.
Search Glean: recent compliance or regulatory announcements requiring legal assessment.
Produce a Word document (.docx) with:
- Contract reviews in queue ranked by deadline (urgent < 7 days first)
- NDA requests: self-service vs complex requiring manual review
- Regulatory submissions due this month with document completeness status
- New compliance or policy changes that may affect merchant agreements
Keep to 2 pages.

I need a Monday briefing for the Supply Chain team.
Pull from Jira: open terminal delivery requests, swap orders, collection tickets, and overdue items.
Pull from Confluence: country-specific delivery SLAs and updated device preparation procedures.
Search Glean: Zuper dispatch updates and courier tracking issues reported over the weekend.
Produce a Word document (.docx) with:
- Delivery queue by type (new, swap, collection) with count per country
- Overdue deliveries and failed attempts requiring rebooking
- Device preparation backlog: units awaiting QA, charging, or key injection
- Stock level alerts for any terminal model running low
Keep to 2 pages.

I need a Monday briefing for the Marketing team.
Pull from Jira: content calendar items due this week, campaign production tasks, and localisation tickets.
Pull from Confluence: active campaign briefs, brand guidelines, and Braze communication schedules.
Search Glean: competitor marketing activity, product launches, and any internal announcements affecting campaign messaging.
Produce a Word document (.docx) with:
- Content deadlines this week by channel (blog, email, social, in-app) with owner
- Campaign status: in production, awaiting approval, or live with early performance signals
- Localisation tasks pending across markets (copy-paste backlog)
- Competitive intelligence highlights relevant to active campaigns
Keep to 2 pages.

I need a Monday briefing for the Onboarding team.
Pull from Jira: merchant applications by stage (registration, KYC, CDD, terminal assignment, activation) and any stuck > 14 days.
Pull from Confluence: onboarding process checklists and updated CDD requirements.
Search Glean: recent HubSpot deal handoffs and any internal ops tool or Zuper issues reported last week.
Produce a Word document (.docx) with:
- Pipeline snapshot: application count by stage with week-over-week change
- Bottleneck analysis: merchants stuck in CDD or final-stage follow-up with days waiting
- Terminal delivery coordination items pending with Zuper
- Conversion funnel: application to first settlement rate this month vs target
Keep to 2 pages.

I need a Monday briefing for the Operations team.
Pull from Jira: open operational requests, cross-team tickets, and process exception items.
Pull from Confluence: SOP update status and stale pages flagged for review.
Search Glean: workflow automation bot failure logs and operations team capacity issues from the past week.
Produce a Word document (.docx) with:
- Open request backlog by team with urgency classification
- workflow automation platform recipe failures last week: count, affected workflows, and manual reprocessing needed
- SOPs flagged as stale or missing for active processes
- operations capacity update: sales agent correction volume and bank account currency changes
Keep to 2 pages.

I need a Monday briefing for the Partnerships team.
Pull from Jira: partner onboarding tickets, integration requests, and commission dispute cases.
Pull from Confluence: partner programme documentation and commission model governance updates.
Search Glean: HubSpot partner pipeline activity and Referral Factory lead attribution from the past week.
Produce a Word document (.docx) with:
- Partner lead generation: new leads by partner this week vs last week
- Integration status: partners in onboarding pipeline with next milestone
- Commission cycle: disputes pending, payments in progress, governance sign-offs needed
- Top and bottom performing partners with suggested follow-up actions
Keep to 2 pages.

I need a Monday briefing for the People team.
Pull from Jira: open HR service desk tickets, onboarding tasks for upcoming new joiners, and off-boarding checklists due.
Pull from Confluence: updated HR policies, onboarding guides, and performance review cycle timeline.
Search Glean: HiBob new joiner announcements, Navan policy queries, and any people-related escalations from Slack.
Produce a Word document (.docx) with:
- New joiners starting this week: names, departments, countries, provisioning status
- Open employee requests by category (access, payroll, benefits, leave queries)
- Off-boardings due this month with handover and access revocation status
- Performance review cycle milestones approaching and completion rates
Keep to 2 pages.

I need a Monday briefing for the Product Activation team.
Pull from Jira: merchants pending activation, blocker tickets (KYC incomplete, terminal not delivered, technical issues).
Pull from Confluence: activation playbooks, campaign templates, and KPI target documentation.
Search Glean: campaign performance results and non-transacting merchant signals from Tableau dashboards last week.
Produce a Word document (.docx) with:
- Activation rate vs 90% POS target: current month progress by lead source
- Non-transacting merchants onboarded > 14 days with likely blocker category
- Campaign effectiveness: conversion rates by channel (SMS, email, phone, ads)
- Drop-off funnel: where merchants are stalling and recommended interventions
Keep to 2 pages.

Pull the current sprint board from Jira — all issues, statuses, assignees.
Search Confluence for the latest product roadmap page.
Search Glean for recent stakeholder decisions.
Produce a Word document (.docx) with:
- Sprint progress (done/in-progress/blocked)
- Issues that need discussion in planning
- Roadmap items relevant to next sprint
- Open decisions that affect scope

I need a Monday briefing for the Product Operations team.
Pull from Jira: Tier 2 escalation queue, complaint records pending audit, and help centre update tickets.
Pull from Confluence: escalation guidelines, complaint handling procedures, and help centre content inventory.
Search Glean: recurring merchant issue patterns reported by CR and Sales in Slack channels last week.
Produce a Word document (.docx) with:
- Tier 2 queue: open escalations by category with average age and resolution path
- Top 5 recurring issue themes with occurrence count and root cause hypothesis
- Complaint audit status: records reviewed vs outstanding with compliance gaps flagged
- Help centre pages due for update based on Tier 2 question frequency
Keep to 2 pages.

I need a Monday briefing for the Retentions team.
Pull from Jira: incoming cancellation requests routed from CR and repricing cases in progress.
Pull from Confluence: save-call framework updates and repricing approval guidelines.
Search Glean: churn signals from Zendesk (fee enquiries, terminal complaints) and HubSpot merchant activity declines.
Produce a Word document (.docx) with:
- Cancellation requests received: count, merchant value, stated reason breakdown
- Save-call prep queue: merchants requiring pre-call data gathering today
- Early warning signals: merchants showing churn indicators but not yet requesting cancellation
- Win-back outcomes from last week: saved, lost, repriced with revenue impact
Keep to 2 pages.

I need a Monday briefing for the Risk team.
Pull from Jira: open risk assessments, merchant reviews pending, and accounts flagged for restriction or blocking.
Pull from Confluence: risk appetite framework, guardrail threshold definitions, and risk model update notes.
Search Glean: chargeback ratio alerts, MOTO pattern warnings, and CDD risk team meeting notes from the past week.
Produce a Word document (.docx) with:
- Merchants under active review: count by risk trigger (chargebacks, fraud, CNP, behaviour mismatch)
- Threshold proximity: merchants within 20% of VAMP or MATCH limits
- Risk model changes or new guardrail rules deployed last week
- Cross-country risk patterns worth raising at the next CDD risk meeting
Keep to 2 pages.

I need a Monday briefing for the Scheme Operations team.
Pull from Jira: open scheme compliance items, bulletin action tickets, and MCC review tasks.
Pull from Confluence: latest Visa, Mastercard, and AMEX bulletin summaries and fee reconciliation procedures.
Search Glean: scheme portal notifications, clearing file issues, and interchange rate changes from the past week.
Produce a Word document (.docx) with:
- Scheme bulletin action items: new mandates, fee changes, or rule updates with deadlines
- Monthly fee reconciliation status: variances flagged by scheme with investigation progress
- MCC compliance: merchants flagged for misclassification or restriction violations
- Upcoming scheme business review preparation items and data pack status
Keep to 2 pages.

I need a Monday briefing for the Treasury team.
Pull from Jira: open settlement funding items, balance correction tickets, and bank transfer exceptions.
Pull from Confluence: treasury policy updates, safeguarding calculation methodology, and banking partner notices.
Search Glean: FX volatility alerts, settlement position reports, and Accounting queries from the past week.
Produce a Word document (.docx) with:
- Safeguarding position: total across partner bank A and partner bank B with 80/20 split check
- Settlement funding status: any shortfalls, failed sweeps, or pending corrections
- FX exposure summary: currencies approaching volatility thresholds and DCC status
- Bank relationship items: portal issues, transfer exceptions, or partner communications requiring action
Keep to 2 pages.

Read the reconciliation pile Excel file. This is Accounting's month-end backlog.
Categorize each item: BLOCKING CLOSE (prevents financial close), VARIANCE (amounts differ between ledger and bank), MISSING EVIDENCE (audit trail incomplete), ROUTINE (standard entries pending posting).
For BLOCKING CLOSE items, draft a one-sentence resolution action with the responsible party.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total unreconciled amount and close readiness %
- BLOCKING CLOSE items with resolution actions and owners
- VARIANCE items grouped by type (currency mismatch, decimal shift, timing difference)
- MISSING EVIDENCE items with the specific document or sign-off needed
- Pattern analysis: recurring reconciliation breaks across accounts or entities
- Recommendation on whether close deadline is achievable

Read the case pile Excel file. This is the Monday pre-arbitration and expiring cases backlog.
Categorize each case: DEADLINE CRITICAL (< 3 days to scheme deadline), EXPIRING SOON (< 7 days), EVIDENCE READY (can submit today), WAITING ON MERCHANT (evidence requested, not received), PRE-ARB ACTION (pre-arbitration response needed).
For DEADLINE CRITICAL cases, draft a one-sentence action plan including scheme portal and deadline date.
Produce a triage report as a Word document (.docx) with:
- Executive summary with case counts by scheme (Visa, Mastercard, AMEX) and urgency
- DEADLINE CRITICAL cases with action plans and scheme portal targets
- PRE-ARB ACTION cases with recommended accept/fight assessment
- Cases grouped by reason code category (Fraud, Consumer Dispute, Processing Error, Authorization)
- Pattern analysis: merchants generating repeat chargebacks or approaching VAMP/MATCH thresholds
- Recommendation for today's case processing order

Read the alert pile Excel file. These are screening alerts requiring review.
For each alert, categorize as: FALSE POSITIVE, NEEDS REVIEW, or ESCALATE.
Draft a one-sentence rationale for each categorization.
Produce a triage report as a Word document (.docx) with:
- Executive summary: counts by category
- ESCALATE items first with full rationale
- NEEDS REVIEW items with suggested next steps
- FALSE POSITIVE items grouped by dismissal reason
- Any cross-alert patterns (same merchant, same geography, same alert type)

Read the escalation pile Excel file. This is the Country Operations escalation backlog across all markets.
Categorize each item: REGULATORY RISK (compliance or legal deadline), MERCHANT OUTAGE (revenue-impacting), LOCAL APPROVAL NEEDED (pending country-specific sign-off), CENTRAL COORDINATION (requires HQ team input), ROUTINE LOCAL (standard local process).
For REGULATORY RISK items, draft a one-sentence action with the affected market and deadline.
Produce a triage report as a Word document (.docx) with:
- Executive summary with escalation counts by country (GB, ES, IT, PT, CZ, HU, IS)
- REGULATORY RISK items with market-specific deadlines and owners
- MERCHANT OUTAGE items with estimated revenue impact
- Escalations grouped by type (sales, onboarding, operations, compliance)
- Pattern analysis: countries or processes generating disproportionate escalations
- Recommendation on which markets need immediate Country Manager attention

Read the ticket pile Excel file. This is the weekend support backlog.
Categorize each ticket by urgency: URGENT (SLA breach risk), TODAY, THIS WEEK, NEEDS INFO.
For URGENT tickets, draft a one-sentence next step.
Produce a triage report as a Word document (.docx) with:
- Executive summary
- URGENT tickets with next steps
- Tickets grouped by category
- Repeat-issue patterns (3+ tickets for same root cause)
- Recommended FAQ articles to reduce future volume

Read the request pile Excel file. This is the Data team's ad-hoc request backlog.
Categorize each request: EXISTING DASHBOARD (answerable from current Tableau dashboards), QUICK QUERY (one-off Snowflake SQL, < 30 min), NEW MODEL NEEDED (requires DBT model or new data source), BLOCKED (upstream data quality issue or missing access), DUPLICATE (same question already answered).
For EXISTING DASHBOARD requests, draft a one-sentence response pointing to the specific dashboard.
Produce a triage report as a Word document (.docx) with:
- Executive summary with request counts by complexity and requesting department
- BLOCKED requests with the specific upstream issue preventing delivery
- NEW MODEL NEEDED items with estimated effort and dependencies
- DUPLICATE clusters for consolidation
- Pattern analysis: departments submitting repeat requests that should be self-serve dashboards
- Recommendation for this week's on-call rotation on-call priorities

Read the exception pile Excel file. This is Finance's settlement and correction backlog.
Categorize each item: UNRECONCILED (bank vs internal mismatch > 48 hrs), CORRECTION PENDING (four-eye approval needed), CURRENCY MISMATCH (FX or currency code discrepancy), SCHEME FORMAT ERROR (Visa/MC/AMEX file parsing issue), ROUTINE (within tolerance, auto-clear candidate).
For UNRECONCILED items, draft a one-sentence investigation step with the data source to check.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total unreconciled value and correction queue depth
- UNRECONCILED items with investigation steps and age in days
- CORRECTION PENDING items with approval status (Pending Approval 1 / Pending Approval 2)
- Items grouped by scheme settlement source (Visa, Mastercard, AMEX)
- Pattern analysis: recurring discrepancy types (decimal shifts, timing gaps, duplicate postings)
- Recommendation on items to escalate via Jira vs resolve directly

Read the alert pile Excel file. This is the Fraud team's monitoring case backlog.
Categorize each alert: BLOCK IMMEDIATELY (high-severity score > 90 or BIN attack pattern), INVESTIGATE (suspicious pattern needing analyst review), FALSE POSITIVE LIKELY (matches known snooze patterns), THRESHOLD WARNING (merchant approaching VAMP/MATCH limits), DUPLICATE (same merchant, same rule, already open case).
For BLOCK IMMEDIATELY alerts, draft a one-sentence recommended action (block payouts, block account, or create ticket).
Produce a triage report as a Word document (.docx) with:
- Executive summary with alert counts by rule type and severity
- BLOCK IMMEDIATELY alerts with recommended actions
- THRESHOLD WARNING merchants with current ratio vs VAMP/MATCH limits
- Alerts grouped by detection mode (real-time, near real-time, batch)
- Pattern analysis: BIN attack clusters, velocity spikes, or coordinated fraud across merchants
- Recommendation for today's queue assignment priorities

Read the deal pile Excel file. This is the pipeline backlog.
Categorize each deal: HOT (ready to close), WARM (needs follow-up), STALE (no contact > 14 days), DATA ERROR (suspicious values).
For HOT deals, draft a call prep brief.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total pipeline value by category
- HOT deals with call prep briefs
- STALE deals with recommended re-engagement approach
- DATA ERROR items for CRM cleanup

Read the ticket pile Excel file. This is the IT Helpdesk's JSM backlog.
Categorize each ticket: P1 INCIDENT (system outage or security issue), ACCESS URGENT (new joiner starting today/tomorrow), ROUTINE ACCESS (standard provisioning request), HARDWARE (equipment issue or replacement), MFA/PASSWORD (reset or lockout), LICENCE REQUEST (software approval needed).
For P1 INCIDENT tickets, draft a one-sentence impact assessment and escalation path.
Produce a triage report as a Word document (.docx) with:
- Executive summary with ticket counts by category and SLA status
- P1 INCIDENT items with impact assessment and escalation contacts
- ACCESS URGENT items with the new joiner's start date and department
- Tickets grouped by application (Okta, Zendesk, HubSpot, Jira, other)
- Pattern analysis: repeated MFA reset abuse, recurring hardware failures, or licence bottlenecks
- Recommendation for ticket assignment across today's support shift

Read the review pile Excel file. This is the contract review backlog.
Categorize each review: URGENT (deadline < 7 days), STANDARD, LOW RISK (template-based), NEEDS ESCALATION (non-standard terms).
For URGENT items, flag the specific clauses requiring attention.
Produce a triage report as a Word document (.docx) with:
- Executive summary
- URGENT reviews with clause-level flags
- NEEDS ESCALATION items with risk description
- Suggested prioritisation for this week

Read the delivery pile Excel file. This is the Supply Chain's terminal order and returns backlog.
Categorize each item: FAILED DELIVERY (courier attempted, merchant not available), OVERDUE (past expected delivery date), PREP NEEDED (device not yet prepared for dispatch), RETURN PENDING QA (returned device awaiting inspection), SWAP URGENT (merchant without working terminal), SCHEDULED (on track, no action needed).
For SWAP URGENT items, draft a one-sentence action with courier and expected resolution.
Produce a triage report as a Word document (.docx) with:
- Executive summary with counts by order type (new, swap, collection, return) and status
- SWAP URGENT and FAILED DELIVERY items with merchant impact and next steps
- OVERDUE items with days past expected date and courier tracking status
- Items grouped by country and delivery partner (DPD, local couriers)
- Pattern analysis: courier failure rates, country-specific delivery bottlenecks, QA backlogs
- Recommendation for today's dispatch and QA priorities

Read the content pile Excel file. This is Marketing's content production and campaign backlog.
Categorize each item: PAST DEADLINE (publication date missed), LAUNCHING SOON (going live within 48 hours, needs approval), IN PRODUCTION (on track, in creative pipeline), NEEDS LOCALISATION (English ready, translations pending), BLOCKED (waiting on Product, Legal, or stakeholder input), BACKLOG (no deadline pressure).
For PAST DEADLINE items, draft a one-sentence recovery plan with revised timeline.
Produce a triage report as a Word document (.docx) with:
- Executive summary with content counts by status and channel (blog, email, social, campaign asset)
- PAST DEADLINE items with recovery plans
- LAUNCHING SOON items with outstanding approval steps
- NEEDS LOCALISATION items grouped by target market and language
- Pattern analysis: bottlenecks in the 40-day campaign cycle (ideation, approval, localisation)
- Recommendation for this week's content priorities by channel

Read the application pile Excel file. This is the Onboarding team's merchant pipeline backlog.
Categorize each application: CDD BLOCKED (KYC/KYB pending > 14 days), DOCUMENT MISSING (merchant hasn't submitted required docs), TERMINAL PENDING (CDD cleared but no device assigned), ALMOST LIVE (all steps complete, awaiting first transaction), AT RISK (> 21 days in any single stage), ON TRACK (progressing normally).
For CDD BLOCKED applications, draft a one-sentence follow-up action with the specific blocker.
Produce a triage report as a Word document (.docx) with:
- Executive summary with pipeline counts by stage (Registration, KYC, CDD, Terminal, Activation)
- CDD BLOCKED and AT RISK applications with days stuck and specific blockers
- DOCUMENT MISSING applications with exactly which documents are outstanding
- Conversion funnel: application to first settlement with drop-off points
- Pattern analysis: lead sources with highest stall rates, CDD bottleneck causes
- Recommendation for follow-up priority and merchants needing escalation to Sales

Read the request pile Excel file. This is the operations request backlog.
Categorize each request: URGENT, ROUTINE, BLOCKED, DUPLICATE.
Flag any requests that appear to be related (same merchant, same issue type).
Produce a triage report as a Word document (.docx) with:
- Executive summary
- URGENT items with recommended actions
- BLOCKED items with what's needed to unblock
- DUPLICATE clusters for consolidation
- Automation failure patterns (bot failures followed by manual requests)

Read the partner pile Excel file. This is the Partnerships team's partner activity and commission backlog.
Categorize each item: COMMISSION DISPUTE (partner querying amount or clawback), UNDERPERFORMING (lead volume dropped > 30% vs prior period), INTEGRATION STUCK (technical onboarding stalled), NEW PARTNER SETUP (onboarding checklist incomplete), CLAWBACK REVIEW (cancelled merchant triggering commission recovery), HEALTHY (performing within expectations).
For COMMISSION DISPUTE items, draft a one-sentence summary of the discrepancy and data to verify.
Produce a triage report as a Word document (.docx) with:
- Executive summary with partner counts by status and total commission value at risk
- COMMISSION DISPUTE items with discrepancy details and verification steps
- UNDERPERFORMING partners with trend data and suggested re-engagement approach
- INTEGRATION STUCK partners with the specific technical blocker
- Pattern analysis: duplicate ISA payments across countries, clawback frequency by partner type
- Recommendation for this week's partner relationship priorities

Read the request pile Excel file. This is the People team's employee request backlog.
Categorize each request: NEW JOINER URGENT (start date within 5 days, setup incomplete), OFF-BOARDING (last day approaching, revocation needed), PAYROLL CRITICAL (affects next pay run), POLICY QUERY (employee question needing response), REVIEW CYCLE (performance review admin task), ROUTINE (standard HR process request).
For NEW JOINER URGENT items, draft a one-sentence checklist gap with the missing setup step.
Produce a triage report as a Word document (.docx) with:
- Executive summary with request counts by category and country
- NEW JOINER URGENT items with start dates and missing provisioning steps
- OFF-BOARDING items with last dates and security-critical access to revoke first
- PAYROLL CRITICAL items with pay run deadline
- Pattern analysis: recurring provisioning delays by department, overdue compliance training
- Recommendation for coordination needed with IT Helpdesk this week

Read the activation pile Excel file. This is Product Activation's non-transacting merchant backlog.
Categorize each merchant: KYC INCOMPLETE (CDD not cleared, can't transact), TERMINAL NOT DELIVERED (device pending logistics), TECHNICAL BLOCKER (setup issue preventing first transaction), DORMANT (onboarded > 30 days, no transaction, no known blocker), CAMPAIGN TARGET (good candidate for activation nudge), ACTIVATED (first transaction processed, remove from list).
For DORMANT merchants, draft a one-sentence outreach action with the suggested channel (SMS, email, phone).
Produce a triage report as a Word document (.docx) with:
- Executive summary with activation rate vs 90% KPI and counts by blocker type
- DORMANT merchants with days since onboarding and suggested outreach
- TECHNICAL BLOCKER merchants with the specific issue to resolve
- Merchants grouped by product type (POS vs E-commerce) and lead source
- Pattern analysis: drop-off points in the activation funnel, campaign conversion rates
- Recommendation for this week's activation campaign targeting

Read the backlog pile Excel file. This is the Product team's Jira backlog.
Categorize each ticket: BLOCKED (dependency or decision preventing progress), SPRINT CARRY-OVER (missed last sprint, needs re-prioritisation), STALE (no update > 14 days), BUG CRITICAL (user-facing defect), READY FOR SPRINT (groomed with acceptance criteria), NEEDS GROOMING (missing requirements or story points).
For BLOCKED tickets, draft a one-sentence unblock action identifying who owns the dependency.
Produce a triage report as a Word document (.docx) with:
- Executive summary with ticket counts by status and total story points at risk
- BLOCKED tickets with dependency owners and suggested unblock actions
- BUG CRITICAL items with severity and affected user segment
- SPRINT CARRY-OVER items with reason for slippage
- Pattern analysis: recurring blockers, teams causing dependencies, velocity trend
- Recommendation for next sprint planning priorities and tickets to descope

Read the escalation pile Excel file. This is Product Operations' Tier 2 escalation backlog from JSM.
Categorize each ticket: PRODUCT BUG (confirmed defect, needs engineering), PROCESS GAP (no runbook or help centre article exists), COMPLAINT (formal complaint requiring GDPR-compliant handling), MISROUTED (should have been resolved at Tier 1), RECURRING PATTERN (3+ instances of same issue), STANDARD RESOLUTION (known fix, can close today).
For PRODUCT BUG items, draft a one-sentence Jira summary for the engineering team.
Produce a triage report as a Word document (.docx) with:
- Executive summary with escalation counts by category and source team (CR, Sales)
- PRODUCT BUG items with Jira summaries ready for engineering handoff
- COMPLAINT items with compliance handling status and response deadline
- RECURRING PATTERN clusters with root cause hypothesis and suggested product fix
- Pattern analysis: help centre content gaps driving Tier 2 volume, misroute rate from Tier 1
- Recommendation for product feedback to share at next Product sync

Read the cancellation pile Excel file. This is the Retention team's incoming cancellation request backlog.
Categorize each request: HIGH VALUE SAVE (monthly volume > threshold, worth a retention call), SERVICE ISSUE (reason linked to support quality, not pricing), PRICE SENSITIVE (competitor offer or fee complaint), BUSINESS CLOSURE (genuine closure, not saveable -- route back to CR), EARLY WARNING (not yet cancelled but showing churn signals), ALREADY LOST (merchant already moved processing elsewhere).
For HIGH VALUE SAVE requests, draft a one-sentence save angle based on the merchant's likely real reason.
Produce a triage report as a Word document (.docx) with:
- Executive summary with cancellation count, total monthly volume at risk, and save opportunity %
- HIGH VALUE SAVE merchants with save-call prep notes and suggested approach
- SERVICE ISSUE cases with the specific service failure to acknowledge
- Cancellation reasons grouped by category (service, price, competitor, closure)
- Pattern analysis: churn signals appearing before formal cancellation, repricing history of churning merchants
- Recommendation for today's retention call priority order

Read the risk alert pile Excel file. This is the Risk team's merchant risk review backlog.
Categorize each alert: RESTRICT NOW (chargeback ratio exceeding VAMP/MATCH threshold), EDD REQUIRED (enhanced due diligence triggered), BEHAVIOUR MISMATCH (transaction pattern inconsistent with declared business type), THRESHOLD APPROACHING (within 20% of scheme limit), PERIODIC REVIEW (standard ongoing monitoring, no red flags), CLEARED (previously flagged, now within acceptable parameters).
For RESTRICT NOW alerts, draft a one-sentence recommended action (monitor, restrict, or block) with the specific threshold breached.
Produce a triage report as a Word document (.docx) with:
- Executive summary with alert counts by severity and scheme (Visa VAMP, Mastercard MATCH)
- RESTRICT NOW alerts with threshold data and recommended actions
- EDD REQUIRED cases with the trigger reason and documentation to request
- BEHAVIOUR MISMATCH merchants with declared vs actual transaction pattern comparison
- Pattern analysis: merchant categories generating repeat alerts, country-level risk concentration
- Recommendation for cases to discuss at the next CDD risk meeting

Read the scheme pile Excel file. This is Scheme Operations' bulletin actions and compliance backlog.
Categorize each item: MANDATE DEADLINE (scheme rule change with implementation date < 30 days), FEE DISCREPANCY (billed vs estimated variance > 5%), MCC NON-COMPLIANT (merchant category code mismatch), CLEARING ERROR (file parsing or format issue), BULLETIN REVIEW (new bulletin needs impact assessment), ROUTINE COMPLIANCE (standard periodic check).
For MANDATE DEADLINE items, draft a one-sentence impact summary with affected teams and implementation date.
Produce a triage report as a Word document (.docx) with:
- Executive summary with item counts by scheme (Visa, Mastercard, AMEX, UnionPay, Diners) and urgency
- MANDATE DEADLINE items with impact summaries and implementation timelines
- FEE DISCREPANCY items with variance amounts by scheme and fee type
- MCC NON-COMPLIANT merchants with current vs correct MCC assignment
- Pattern analysis: schemes generating most compliance work, recurring fee reconciliation breaks
- Recommendation for items to include in the next scheme business review

Read the treasury pile Excel file. This is Treasury's daily liquidity and safeguarding exception backlog.
Categorize each item: FUNDING SHORTFALL (settlement account below required balance), SAFEGUARDING BREACH (80/20 partner bank A/partner bank B split outside tolerance), FX EXPOSURE (currency position approaching volatility threshold), TRANSFER FAILED (automated sweep or manual transfer did not execute), BALANCE CORRECTION (minor adjustment needed), NORMAL (within all parameters).
For FUNDING SHORTFALL items, draft a one-sentence action with the amount needed and target bank account.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total safeguarded balance, split ratio status, and exception count
- FUNDING SHORTFALL items with shortfall amounts and settlement deadlines
- FX EXPOSURE items with current position vs threshold by currency
- TRANSFER FAILED items with the failed sweep details and retry instructions
- Pattern analysis: currencies or bank partners generating repeat exceptions, timing patterns in sweep failures
- Recommendation on DCC currencies to consider disabling and transfers to prioritise today

Build a skill that runs every morning at 7:30am.
It should:
1. Read the latest bank-statement.csv and ledger-entries.csv from the workspace
2. Match entries by Reference_Number and Date
3. Separate into matched, variances, unmatched-bank, and unmatched-ledger
4. Produce a reconciliation report (.docx) with four sections, summary stats, and variance highlights
5. If any single variance exceeds 1,000 or total unmatched entries exceed 10, flag as CRITICAL and prepend a warning banner
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 7am.
It should:
1. Read all cases updated in the past 7 days from Jira
2. Group by scheme (Visa, Mastercard, AMEX)
3. Calculate approaching deadlines (< 7 days warning, < 3 days critical)
4. Produce a Word document (.docx) summary with deadline warnings
5. If any case is < 3 days from deadline, flag as CRITICAL in the summary
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 7am.
It should:
1. Read the daily screening alert export from the workspace (compliance-alerts.xlsx)
2. Categorise each alert as FALSE POSITIVE, NEEDS REVIEW, or ESCALATE based on similarity score and match type
3. Flag cross-alert patterns (same merchant appearing in multiple alerts)
4. Produce a triage summary (.docx) grouped by disposition with counts, escalation cases detailed, and pattern analysis
5. Any ESCALATE case must include the note: DRAFT — analyst must verify all match details before final disposition
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 8am.
It should:
1. Read country-metrics.csv from the workspace covering the past 7 days
2. Calculate week-over-week changes for sales, ticket volume, onboarding, and activation per country
3. Rank countries by performance and flag any metric that dropped more than 15% week-over-week
4. Produce a one-page digest (.docx) with tables, trend arrows, and a top wins / top concerns section per country
5. If any country shows three or more declining metrics simultaneously, flag as NEEDS ATTENTION at the top of the report
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 7:30am.
It should:
1. Read all Zendesk tickets received in the past 24 hours from support-tickets.xlsx
2. Categorise each as Onboarding Status, Terminal Issue, Settlement Query, Chargeback, Complaint, or Other
3. Assign priority (URGENT if merchant cannot process payments, HIGH if revenue impacted, NORMAL otherwise) and route to CR, Tier 2, Chargebacks, Retentions, or CDD
4. Produce a triage report (.docx) sorted by priority with suggested first response for each ticket
5. Any ticket categorised as Complaint must be flagged separately with a reminder to log a formal complaint record
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 6am.
It should:
1. Read the latest data-quality-checks.csv from the workspace (null rates, row counts, freshness per table)
2. Compare each metric against the 30-day rolling average and flag deviations greater than 2 standard deviations
3. Classify anomalies as STALE (freshness), VOLUME (row count shift), or INTEGRITY (null rate spike)
4. Produce an anomaly report (.docx) with a summary dashboard, per-table detail, and suggested investigation steps
5. If any anomaly affects a table feeding the commission pipeline or SAP integration, flag as FINANCIAL IMPACT and escalate to the Data team lead
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 8am.
It should:
1. Check for new settlement files in the workspace
2. Run a quick reconciliation against the internal ledger
3. Flag any discrepancies > 500
4. Produce a brief summary (.docx) — green if clean, yellow if minor issues, red if critical
5. Save to workspace with today's date in filename
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 7am.
It should:
1. Read merchant-chargeback-ratios.csv from the workspace covering the trailing 3 months
2. Calculate current chargeback ratio per merchant and compare against Visa VAMP and Mastercard MATCH thresholds
3. Flag merchants within 20% of either threshold and classify trend as increasing, stable, or decreasing
4. Produce a threshold monitoring report (.docx) with a summary table, flagged merchants detailed section, and 3-month trend charts
5. Any merchant that has crossed or is within 10% of a scheme threshold must be marked CRITICAL — senior fraud analyst review required before any action
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 7:30am.
It should:
1. Read hubspot-pipeline-export.xlsx from the workspace
2. Identify stale deals (not updated in 7+ days), stage bottlenecks, and top 10 deals closest to close
3. Flag at-risk deals where CDD is blocking or a competitor is mentioned in notes
4. Produce a pipeline health report (.docx) with three sections: stale deals with suggested actions, bottleneck analysis, and top 10 priority list
5. Deals stale for more than 14 days must be flagged as REQUIRES IMMEDIATE UPDATE — rep must add a note or close
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 8am.
It should:
1. Read software-licences.csv (tool, licence count, assigned users, last login date) from the workspace
2. Identify unused licences (no login in 30+ days) and orphaned accounts (user left company per HiBob export)
3. Calculate potential cost savings from reclaiming unused seats
4. Produce a licence audit report (.docx) with per-tool summary, unused seat detail, orphaned accounts, and estimated monthly savings
5. Any tool where unused licences exceed 20% of total must be flagged for manager review before reclamation
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 9am.
It should:
1. Read the JSM ticket export for Legal Help Desk requests from the past 7 days (legal-tickets.csv)
2. Categorise by type: NDA, contract review, GDPR request, regulatory submission, or other
3. Calculate ageing for each open request and flag any approaching SLA breach
4. Produce a legal workload report (.docx) with open items by category, ageing distribution, SLA risk items, and completed items summary
5. Any GDPR subject access request older than 20 days must be flagged as SLA CRITICAL — escalate to Data Privacy team immediately
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 7am.
It should:
1. Read delivery-queue.csv from the workspace covering all open terminal orders
2. Classify each order as On Track, Arriving Today, or Overdue based on expected delivery date
3. Count orders by type (new, swap, collection) and summarise returns pending QA
4. Produce a delivery status report (.docx) with today's schedule, overdue orders with courier details, and QA backlog
5. Any order overdue by more than 3 business days must be flagged as ESCALATE — contact courier and notify the merchant
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 8am.
It should:
1. Read campaign-results.csv from the workspace covering all active campaigns from the past 7 days
2. Calculate week-over-week change in open rate, click rate, conversion, and cost per acquisition per campaign
3. Flag any campaign with declining performance for two consecutive weeks
4. Produce a campaign performance digest (.docx) with per-campaign summary table, channel comparison, and top/bottom performers
5. If any campaign shows a conversion drop greater than 30% week-over-week, flag as REVIEW URGENTLY before next spend is committed
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 8am.
It should:
1. Read onboarding-pipeline.csv from the workspace listing all merchants in the onboarding journey
2. Identify the current stage for each merchant (Registration, KYC, CDD, Terminal, Activation) and calculate days in stage
3. Flag merchants as AT RISK if stuck in any stage for 14+ days, or BLOCKED if CDD pending for 21+ days
4. Produce a pipeline status report (.docx) with full pipeline table, bottleneck summary, and conversion funnel metrics
5. Any merchant in BLOCKED status for 28+ days must trigger a note: ESCALATE to Onboarding Lead — potential merchant loss
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 7:30am.
It should:
1. Read workato-failures.csv from the workspace listing all workflow automation bot recipe failures in the past 24 hours
2. Group failures by recipe name and error type, and count occurrences
3. Identify repeat offenders (recipes that failed 3+ times) and newly failing recipes (first failure in 7 days)
4. Produce a failure summary (.docx) with total failures, top failing recipes, error patterns, and suggested reprocessing steps
5. If any recipe failure affects merchant settlements or financial corrections, flag as FINANCIAL IMPACT — must be manually reprocessed before end of day
Use /skill-creator to build the skill definition.

Build a skill that runs on the 1st of each month at 8am.
It should:
1. Read commission-data.csv and partner-activity.csv from the workspace for the previous month
2. Calculate total commission per partner with breakdown by merchant, applying clawback rules for cancelled merchants
3. Flag anomalies: commissions changing more than 50% month-over-month, duplicate entries, or partners earning across multiple countries
4. Produce a commission report (.docx) with per-partner summary, detailed breakdown, anomaly section, and comparison vs prior month
5. Any flagged anomaly must include the note: REQUIRES SIGN-OFF — commission governance process mandates documentation before payment to SAP
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 8am.
It should:
1. Read upcoming-joiners.csv from the workspace listing all new joiners starting in the next 14 days
2. Check readiness for each: HiBob account created, IT ticket raised, equipment ordered, onboarding schedule drafted
3. Flag any joiner starting within 5 days who has incomplete items as AT RISK
4. Produce a new joiner readiness report (.docx) with per-joiner checklist, completion status, and department breakdown
5. If any joiner is starting in 2 or fewer business days with missing system access, flag as URGENT — escalate to IT Helpdesk immediately
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 8am.
It should:
1. Read activation-data.csv from the workspace for all merchants onboarded in the past 30 days
2. Identify merchants with no first transaction and classify the likely blocker (KYC incomplete, terminal not delivered, technical issue, or unknown)
3. Flag merchants 14+ days post-onboarding with no transaction as AT RISK
4. Produce a non-transacting merchant report (.docx) with full status table, blocker breakdown, and suggested outreach actions per merchant
5. Before sending any outreach, check with Sales to avoid duplicate messaging — include a coordination note on every merchant flagged for contact
Use /skill-creator to build the skill definition.

Build a skill that runs every Friday at 4pm.
It should:
1. Read jira-sprint-export.xlsx from the workspace for the current sprint
2. Calculate completed vs carried-over story points, bugs found vs fixed, and velocity trend over the last 4 sprints
3. Extract blockers and open dependencies from ticket comments and labels
4. Produce a sprint summary (.docx) with completion stats, carried-over items with reasons, blocker list, and next sprint risks
5. Any blocker that has been unresolved for more than 5 business days must be flagged as ESCALATE — PM to raise in next leadership sync
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 8am.
It should:
1. Read tier2-tickets-month.csv from the workspace covering all Tier 2 escalations from the past 7 days
2. Group tickets by issue category and count occurrences, comparing against the previous week
3. Identify the top 5 recurring themes with root cause hypothesis and affected merchant segment
4. Produce a recurring issue report (.docx) with pattern table, trend comparison, and product fix recommendations for each theme
5. Any issue category that increased more than 50% week-over-week must be flagged as TRENDING — notify Product team for prioritisation
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 7:30am.
It should:
1. Read merchant-activity.csv from the workspace covering transaction volumes, support tickets, and fee enquiries for the past 30 days
2. Flag merchants showing early warning signals: volume decline greater than 20% month-over-month, recent complaints, fee enquiries, or terminal issues
3. Rank flagged merchants by estimated churn probability based on signal count and severity
4. Produce a churn early warning report (.docx) with ranked at-risk merchants, signal detail per merchant, and suggested intervention (call, reprice, or escalate)
5. Any merchant with monthly volume above 50K showing 3+ warning signals must be tagged as HIGH VALUE AT RISK — Retentions lead must review before outreach
Use /skill-creator to build the skill definition.

Build a skill that runs every Monday at 7am.
It should:
1. Read merchant-risk-data.csv from the workspace with chargeback ratios, refund rates, and transaction patterns per merchant
2. Calculate distance from Visa VAMP and Mastercard MATCH thresholds for each merchant
3. Classify 3-month trend as increasing, stable, or decreasing and flag merchants within 20% of any threshold
4. Produce a threshold monitoring report (.docx) with summary dashboard, flagged merchants with full detail, and trend analysis
5. Any merchant that has breached or is within 10% of a scheme threshold must be marked as CRITICAL — senior risk analyst must review before any restrict or block action
Use /skill-creator to build the skill definition.

Build a skill that runs on the 5th of each month at 8am.
It should:
1. Read scheme-fees.csv (billed by schemes) and internal-estimates.csv (our calculations) from the workspace
2. Match by Scheme, Month, and Fee_Type, then calculate variance in amount and percentage
3. Flag any variance exceeding 5% or 1,000 and group discrepancies by scheme
4. Produce a fee reconciliation report (.docx) with matched summary, flagged discrepancies with detail, and per-scheme totals
5. Any discrepancy affecting interchange pass-through fees must be flagged as FINANCIAL REVIEW REQUIRED — Finance team must confirm before scheme is contacted
Use /skill-creator to build the skill definition.

Build a skill that runs every morning at 7am.
It should:
1. Read safeguarding-data.csv and fx-positions.csv from the workspace
2. Verify the 80/20 safeguarding split between partner bank A and partner bank B and flag any drift beyond 2 percentage points
3. Check each currency position against volatility thresholds and flag currencies approaching limits
4. Produce a morning treasury brief (.docx) with safeguarding summary, split check, FX exposure table, and DCC status per currency
5. If any currency has breached its volatility threshold or safeguarding split has drifted beyond 5 points, flag as IMMEDIATE ACTION REQUIRED — Treasury lead must review before market open
Use /skill-creator to build the skill definition.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open accounting tickets and month-end tasks.
Pull from Confluence: updated accounting procedures and close calendars.
Produce a Word document (.docx) with:
- RED: Items past close deadline
- YELLOW: Reconciliations pending review
- GREEN: Completed items
If any RED items exist past close deadline, draft escalation.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: all cases with status changes overnight.
Pull from Confluence: any scheme bulletin updates.
Combine with: yesterday's unresolved items from my workspace.
Produce a Word document (.docx) with:
- RED: Cases < 3 days from deadline
- YELLOW: Cases needing attention today
- GREEN: Cases on track
- New scheme bulletins requiring action
If any RED items exist, draft a separate escalation summary.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open CDD cases and EDD reviews due this week.
Pull from Confluence: updated regulatory guidance and policy changes.
Search Glean: sanctions screening tool alerts from past 24 hours.
Produce a Word document (.docx) with:
- RED: Cases past SLA or flagged for MLRO escalation
- YELLOW: EDD reviews due within 48 hours
- GREEN: Cases progressing on schedule
- New regulatory updates requiring action
If RED cases > 3, draft MLRO escalation summary.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: country-level operational issues and merchant escalations.
Pull from Confluence: market-specific runbooks and compliance updates.
Produce a Word document (.docx) with:
- RED: Regulatory deadlines or merchant outages
- YELLOW: Pending local partner approvals
- GREEN: Operations running normally
If any market has a regulatory deadline within 7 days, flag separately.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: overnight escalations and SLA breaches.
Pull from Confluence: updated runbooks and known issues.
Search Glean: relevant announcements from past 24 hours.
Produce a Word document (.docx) with:
- RED: SLA breaches requiring immediate action
- YELLOW: Escalations pending response
- GREEN: Resolved overnight items
- Trending issues (same category appearing 3+ times)
If SLA breaches > 5, draft escalation to team lead.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open data requests and pipeline incidents.
Pull from Confluence: Snowflake migration status and dashboard change log.
Produce a Word document (.docx) with:
- RED: Pipeline failures or data quality alerts from overnight
- YELLOW: Ad-hoc requests pending > 24 hours
- GREEN: Pipelines healthy, dashboards current
If any pipeline failure occurred overnight, include error summary.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: settlement exceptions and financial correction requests.
Pull from Confluence: month-end close checklist progress.
Produce a Word document (.docx) with:
- RED: Unreconciled settlements past 48 hours
- YELLOW: Financial corrections awaiting four-eye approval
- GREEN: Settlements matched and processed
If unreconciled amount > threshold, draft escalation to finance lead.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: overnight fraud alerts and monitoring case queue.
Pull from Confluence: updated fraud pattern bulletins.
Produce a Word document (.docx) with:
- RED: High-severity alerts (score > 90) requiring immediate review
- YELLOW: Merchants approaching VAMP/MATCH thresholds
- GREEN: Cleared false positives from overnight
- BIN attack or velocity spike patterns detected
If any merchant exceeds 0.9% chargeback ratio, flag for scheme review.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: CDD status updates on pending merchant applications.
Search Glean: overnight inbound leads and HubSpot deal card changes.
Produce a Word document (.docx) with:
- RED: Deals at risk of stalling (no activity > 5 days)
- YELLOW: CDD pending items blocking onboarding handoff
- GREEN: Deals progressing through pipeline
- Today's call list with pre-call context
If any deal is past SLA for CDD response, flag for follow-up.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open IT tickets, overnight incidents, and SLA status.
Pull from Confluence: known issues and maintenance windows.
Produce a Word document (.docx) with:
- RED: P1/P2 incidents still open from overnight
- YELLOW: Tickets approaching SLA breach
- GREEN: Resolved overnight items
If any P1 incident is open, draft all-hands notification.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open legal review requests and contract approvals.
Pull from Confluence: regulatory update tracker and policy changes.
Produce a Word document (.docx) with:
- RED: Contract reviews past deadline
- YELLOW: Regulatory changes requiring legal assessment
- GREEN: Reviews completed and approved
If any regulatory change impacts merchant agreements, flag for review.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: terminal delivery and swap requests pending.
Search Glean: Zuper dispatch status and field engineer availability.
Produce a Word document (.docx) with:
- RED: Failed deliveries or missed SLA windows
- YELLOW: Deliveries scheduled today needing confirmation
- GREEN: Completed installations and swaps
If any delivery failed twice, escalate to logistics manager.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: content calendar items due this week.
Pull from Confluence: campaign briefs and brand guidelines updates.
Search Glean: competitor announcements from past 24 hours.
Produce a Word document (.docx) with:
- RED: Content past publication deadline
- YELLOW: Campaigns launching within 48 hours needing approval
- GREEN: Scheduled content on track
If any competitor launched a relevant feature, draft competitive brief.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: merchant applications in pipeline and CDD clearance status.
Pull from Confluence: onboarding process checklists.
Produce a Word document (.docx) with:
- RED: Applications stalled > 5 business days
- YELLOW: CDD pending items blocking activation
- GREEN: Applications progressing normally
- Conversion funnel: application to first settlement
If stalled applications > 10, draft bottleneck analysis.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: operational incidents and process exceptions.
Pull from Confluence: updated SOPs and operational playbooks.
Produce a Word document (.docx) with:
- RED: Active incidents or system outages
- YELLOW: Process exceptions needing manual intervention
- GREEN: Operations running within normal parameters
If any system is degraded, include impact assessment.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: partner integration requests and referral pipeline.
Pull from Confluence: partner programme documentation updates.
Produce a Word document (.docx) with:
- RED: Partner SLA breaches or integration failures
- YELLOW: Referral deals pending partner confirmation
- GREEN: Active integrations running normally
If any partner integration has been down > 24 hours, draft escalation.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open HR tickets and employee requests.
Pull from Confluence: policy updates and onboarding checklists.
Produce a Word document (.docx) with:
- RED: Employee issues past response SLA
- YELLOW: New starter onboarding items due this week
- GREEN: Resolved requests and completed onboardings
If any compliance training is overdue for > 5 employees, flag.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: merchants pending feature activation and adoption blockers.
Pull from Confluence: product release notes and activation playbooks.
Produce a Word document (.docx) with:
- RED: Merchants past activation SLA (onboarded but not transacting)
- YELLOW: Feature rollouts pending merchant confirmation
- GREEN: Successfully activated merchants this week
If activation rate drops below target, include root cause analysis.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: sprint board status, blocked tickets, and new bugs.
Pull from Confluence: PRD review comments and stakeholder feedback.
Produce a Word document (.docx) with:
- RED: Blocked tickets or sprint-at-risk items
- YELLOW: PRDs awaiting stakeholder sign-off
- GREEN: Sprint items on track
- Upcoming: items due for WBR/QBR preparation
If sprint velocity is trending below target, flag.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: product incidents, feature flag changes, and rollback requests.
Pull from Confluence: release calendar and operational readiness checklists.
Produce a Word document (.docx) with:
- RED: Active product incidents or failed deployments
- YELLOW: Releases scheduled for today needing go/no-go
- GREEN: Systems stable, no pending rollbacks
If any deployment failed overnight, include rollback status.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: cancellation requests and win-back cases.
Search Glean: merchant churn signals from support tickets.
Produce a Word document (.docx) with:
- RED: High-value merchants requesting cancellation
- YELLOW: Merchants with declining transaction volumes
- GREEN: Successful win-backs and renewed contracts
If any merchant with MRR > threshold requests cancellation, flag immediately.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: open risk assessments and merchant risk reviews.
Pull from Confluence: risk appetite framework and threshold updates.
Produce a Word document (.docx) with:
- RED: Merchants exceeding risk thresholds or pending suspension
- YELLOW: Risk reviews due within 48 hours
- GREEN: Merchants within acceptable risk parameters
If any merchant triggers multiple risk indicators, draft review summary.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: scheme compliance items and bulletin action items.
Pull from Confluence: Visa/Mastercard/AMEX bulletin summaries.
Produce a Word document (.docx) with:
- RED: Scheme deadlines within 7 days
- YELLOW: New scheme bulletins requiring action
- GREEN: Compliance items on track
If any scheme mandate has an approaching deadline, draft impact assessment.

Build a morning dashboard that runs at 7am daily.
Pull from Jira: settlement funding items and liquidity alerts.
Pull from Confluence: treasury policy updates and banking partner notices.
Produce a Word document (.docx) with:
- RED: Funding shortfalls or failed settlement sweeps
- YELLOW: Accounts approaching balance thresholds
- GREEN: All funding positions within normal range
If any settlement funding gap exceeds threshold, draft escalation to CFO.