Workshop 2: Connect Everything illustration
Workshop 02Beginner90 minEveryone

Connect Everything

Make Cowork read from and write to your work systems

What you'll learn5 objectives
  • Connect Cowork to your project management, documentation, and enterprise search tools via MCP connectors
  • Build a cross-system briefing that pulls live data from multiple sources in a single prompt
  • Apply the Connector Hierarchy decision tree to determine the right integration method for any tool
  • Verify cross-system outputs using the Traffic Light framework from Workshop 1
  • Install and test skills from the marketplace that leverage your new MCP connections
0 of 8
1

Promise Check-In

Intro

Did you run last week's Monday Promise? 30-second share: what happened, what surprised you.

2 min

Last week's Monday Promise — who ran it? 30-second share with your neighbour. The gap between intention and action is what we close today.

Who actually ran their Monday Promise?
Quick 30-second share: what happened? What surprised you?

This week we connect your tools so the data flows automatically.

2

The Voice Note

Intro

Watch a rough 30-second voice memo turn into a structured briefing with decisions, actions, and open questions — pulled from live connected systems.

3 min

Phone. Voice memo. Thirty seconds. Sixty seconds later: a two-page briefing with live data from Jira, Confluence, and enterprise search. No uploads. No copy-paste.

Workshop 1 was I feed Cowork data. Workshop 2 is Cowork fetches its own.

Workshop 1 was "I feed Cowork data." Workshop 2 is "Cowork fetches its own data." From today, Cowork goes and gets what it needs directly from the source.
3

MCP Deep Dive

Step-by-Step

Connect Cowork to Atlassian, Glean, and your other tools using MCP — so prompts can read from and write to your real work systems without copy-pasting.

20 min

MCP (Model Context Protocol) is the structured, authenticated pipe from Cowork to your work systems — no screen-scraping, no copy-paste.

Eight minutes, three connections. Then reach for the right tier for each tool you still can't connect.

MCP Connectors

Structured API connections — reliable, fast, always prefer these

  • Project management
  • Documentation platform
  • Enterprise search
  • Team messaging

Tool has a supported MCP connector

Chrome Automation

Visual browser automation — slower but works for any web-based tool

  • Analytics dashboards
  • Internal admin portals
  • Scheme dispute portals
  • Terminal management interfaces

Tool has a web interface but no MCP connector

Manual Export

Download file, drop into workspace — fallback when nothing else works

  • Bank portals
  • PDF reports from partners
  • Email attachments
  • Legacy systems

Tool has no MCP connector and no navigable web UI

1
Does this tool have an MCP connector?

Yes: Use MCP. Always. Fastest, most reliable, structured data.

No: Go to question 2.

2
Does this tool have a web interface I can access?

Yes: Use Chrome automation. Slower but flexible. Works for dashboards and portals.

No: Go to question 3.

3
Can I export the data as a file?

Yes: Manual export. Download CSV/PDF/Excel and drop into workspace.

No: Contact IT — the tool may need an integration built.

Ideal For

  • Tools with web dashboards but no API
  • Visual snapshots for reports (screenshots, charts)
  • Frequently changing data (live queues, real-time metrics)
  • Read-only operations on internal portals

Not Ideal For

  • Tools requiring MFA on every visit
  • Pages with frequently changing layouts
  • Large dataset processing (10,000+ rows)
  • Speed-critical operations
The hierarchy is about reliability, not capability. MCP connectors are not better because they can do more — Chrome automation can interact with almost anything. MCP is better because it fails less. In a FinTech environment where accuracy matters, prefer the most reliable integration method available.
4

Skills Marketplace

Step-by-Step

With MCP connected, skills upgrade from file-based to live-data. Install your first skill and run it against a real system to feel the difference.

10 min

Skills that used to require a CSV export now query the source. Pick two below that match your week, install, run one right now with live data.

/sun:jira-briefing

Pulls project management data via MCP, generates formatted briefing

Required CSV export or pasted ticket list

Queries project management tool directly for live data

/sun:research

Searches across connected enterprise tools

Limited to files in workspace

Searches documentation, messaging, project management, and more

/sun:evidence-assembler

Assembles dispute evidence packages

Required manual case detail input

Pulls case details directly from project management

/sun:ticket-triage

Categorizes and prioritizes support tickets

Required CSV export of ticket queue

Reads live queue directly

/sun:pipeline-analyzer

Analyzes pipeline health and flags stale deals

Required CRM export

Pulls live deal data via MCP or Chrome automation

Install and Test
1Pick 2 skills from the list that match your role
2Install each by typing the command and following installation prompts
3Run one skill immediately with your live MCP data
4Verify the output matches what you see in the source system

In-House

Built by your company, tested against your data

  • All /sun: skills

Official

Published by verified authors, reviewed for quality

  • /xlsx
  • /docx
  • /pptx
  • /pdf

Community

Published by community members, not reviewed

  • Third-party skill packs
Install 2-3 skills that match your weekly workflows. Use them for a week, then decide whether to keep or swap. Quality over quantity.
5

Cross-System Briefing Challenge

Try It

Pull live data from Jira, Confluence, and your CRM in one prompt — no file uploads, no copy-pasting — into a single formatted briefing document.

⏱ 25 min25 min
Challenge
25:00

Main event. One prompt. Three systems. One 2-page Word doc. Watch the activity log light up with live tool calls — then refine for your role in the Prompts tab.

0/5 complete

Stretch Challenges

  • Add a local data source: Cross-reference a workspace file with live MCP data in your briefing
  • Publish to documentation platform: Use /sun:publish to push verified briefing to your team's space
The universal prompt is deliberately broad. Your department-specific prompt narrows it with filters and flagging rules tailored to your workflow.
6

Verification Practice

Safety

Your multi-source briefing looks authoritative. Apply the Traffic Light method to catch errors before you trust data that came from three different systems.

10 min

Your briefing looks authoritative — live data, clean headings, specific action items. Don't trust it yet. Five minutes to find at least two factual errors. Then swap with a neighbour.

Exercise

Individual

Find at least 2 factual errors in your briefing. Correct them.

5 min

Group

Swap briefings with your neighbour. Can they spot an error you missed?

3 min

Issue counts

Compare the number of issues in the briefing to what you see on the actual board

Common error: Cowork may exclude subtasks, include items from a different project, or miss recently updated issues

Links and references

Click every documentation link in the briefing. Does it exist? Is it the right page?

Common error: Cowork occasionally generates plausible-looking page titles that do not correspond to real pages

Dates and timelines

Verify relative dates (last Tuesday, 3 days ago) against actual creation dates

Common error: Cowork miscalculates relative dates, especially around weekends and holidays

Attribution accuracy

Verify that quoted information actually comes from the cited source

Common error: Cowork sometimes mixes up which source said what when pulling from multiple tools

Recommendation quality

Check that recommended actions are specific, actionable, and follow from the data

Common error: Generic filler recommendations that do not reference specific issues

A cross-system briefing is only as reliable as its weakest source. If Cowork pulled from three systems and you verified two of them, the unverified one is where the error lives. Verify all sources. Every time. No exceptions.
7

The Gap Finder

Exercise

Find the 5 questions your briefing cannot answer — because those systems have no MCP connector yet. This gap is your automation wishlist.

15 min

Your briefing connects 3 systems. Which 5 questions can it still not answer — and which of those hurt the most? That's your automation wishlist.

Your turn
1

Read the 5 gap questions in gap-questions.md

2

For each question, identify which system holds the answer

3

Note which of these systems you currently check manually every day

4

Discuss with the person next to you: which gap causes the most pain in your daily work?

Which gap causes the most pain in your daily work?

Pair discussion with neighbour

8

Monday Promise

Practice

Monday, run your cross-system briefing with live data, verify it, share it with your team — not try it, do it.

5 min

Monday, run your cross-system briefing with live data, verify it, share it with your team — not try it, do it.

The Monday Promise is not about the briefing. It is about the habit. If you run a cross-system briefing every Monday for 4 weeks, it stops being a workshop exercise and starts being how you work. That is when the sunshine minutes compound.

Steal This Prompt

Copy these prompts, customize the file paths to match your workspace, and use them in Cowork. Replace ~ with your actual home directory path if needed.

Month-End Close Readiness Briefing

Start here
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-e...
Show full prompt
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.
Accounting

Pending Case Deadline Briefing

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) briefin...
Show full prompt
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.
Chargebacks

Weekly Alert Backlog and EDD Status Briefing

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:...
Show full prompt
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.
Compliance / CDD

Country Performance and Escalation Briefing

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 f...
Show full prompt
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.
Country Operations

Weekend Escalation Summary

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 th...
Show full prompt
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)
Customer Relations

Data Team Requests and Pipeline Health Briefing

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: Snowfl...
Show full prompt
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.
Data / Analytics

Month-End Status Briefing

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 ...
Show full prompt
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
Finance

Fraud Monitoring and Scheme Threshold Briefing

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 Confl...
Show full prompt
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.
Fraud

Pipeline Health and CDD Handoff Briefing

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: update...
Show full prompt
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.
Inside Sales

IT Ticket Queue and Access Request Briefing

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. ...
Show full prompt
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.
IT / Helpdesk

Contract Review and Regulatory Deadline Briefing

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 Conf...
Show full prompt
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.
Legal

Terminal Delivery and Returns Status Briefing

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: count...
Show full prompt
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.
Logistics / Supply Chain

Campaign Calendar and Competitive Intel Briefing

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: ac...
Show full prompt
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.
Marketing

Merchant Onboarding Pipeline Briefing

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. ...
Show full prompt
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.
Onboarding

Ops Process Health and Bot Failure Briefing

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 statu...
Show full prompt
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.
Operations

Partner Performance and Commission Briefing

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 pr...
Show full prompt
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.
Partnerships

People Team Weekly Activity Briefing

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 Co...
Show full prompt
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.
People / HR

Activation Rate and Campaign Briefing

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). ...
Show full prompt
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.
Product Activation

Sprint Planning Brief

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. Pro...
Show full prompt
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
Product Management

Tier 2 Escalation and Recurring Issue Briefing

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 Conflu...
Show full prompt
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.
Product Operations

Cancellation Queue and Churn Signal Briefing

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 fra...
Show full prompt
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.
Retention

Merchant Risk Review and Threshold Briefing

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:...
Show full prompt
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.
Risk

Scheme Compliance and Fee Reconciliation Briefing

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 V...
Show full prompt
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.
Scheme Operations

Liquidity Position and Safeguarding Briefing

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: treas...
Show full prompt
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.
Treasury

Key Takeaways

  1. MCP connectors give Cowork direct, structured access to your work systems — no more copy-pasting between browser tabs

  2. The Connector Hierarchy (MCP > Chrome > Manual Export) helps you pick the most reliable integration for each tool

  3. Cross-system briefings are powerful but must be verified — synthesizing multiple sources multiplies both value and error risk

  4. Skills become dramatically more useful with MCP connections — the same skill that needed a CSV export now pulls live data

  5. The Monday briefing habit compounds over time — four weeks of consistent use turns a workshop exercise into how you work

Safety Note

Cross-system briefings combine data from multiple sources. This multiplies both the value and the risk.

  • Never include raw customer PII in briefings. Use merchant IDs instead of names.
  • Verify before sharing. Every error in a briefing is your error, not Cowork's. Run the verification checklist every time.
  • MCP connections inherit your permissions. Cowork can only see what you can see — but if you have access to sensitive data, so does Cowork. Be mindful of what you pull and where you store the output.
  • Do not publish unverified briefings. A wrong number in a shared briefing is worse than a wrong number on your laptop.
  • Review write operations. MCP write operations (creating tickets, updating pages) are permanent. Always review before confirming.