First Blood
Set up your identity and automate your first task

1Your Identity
Step-by-Step6 steps to complete
10 min
Your Identity
Step-by-Step6 steps to complete
Your Identity
10 minCreate your workspace folder. Mac: open Terminal, type mkdir ~/Cowork-Workspace and press Enter. Windows: open File Explorer, navigate to your user folder, create a new folder called Cowork-Workspace.
Grant Cowork access to your workspace folder. Open Claude Desktop. Click the Cowork tab. When prompted, select ONLY the Cowork-Workspace folder you just created.
Download your data pack from the workshop portal link on the screen. Select your department. Download the zip file. Extract it into Cowork-Workspace. You should see two Excel files and the data-pack-info.md file.
Run /sun:workspace in Cowork. Answer the department and role questions. It will generate a CLAUDE.md file customised to your department.
Review your CLAUDE.md. Open it in a text editor. Does it describe your job accurately? Does it list the right tools? Edit anything that is wrong — this file is yours.
Verify setup. Ask Cowork: List all files in my workspace folder. Tell me the filename, type, and size of each.
2The Monday Morning Massacre
IntroThese were controlled demos. The data was clean. The connections were pre-configured. The prompts we
5 min
The Monday Morning Massacre
IntroThese were controlled demos. The data was clean. The connections were pre-configured. The prompts we
The Monday Morning Massacre
5 minIt is 9:01am on Monday. You have 47 unread messages. A Jira board you have not looked at since Thursday. Twenty-five support tickets from the weekend. A sprint review at 9:30 that you have not prepped for. Someone has already sent the dreaded 'quick question' message — which is never quick.
This is the Monday Morning Massacre. Every week. Same ritual. Two hours of your morning burned just catching up on what happened while you were away, before you can start doing real work.
Watch closely. The facilitator is going to clear three Monday morning tasks in under two minutes.
3Your First Kill — Reconciliation
Try ItTimed challenge — 10 min
⏱ 10 min37 min
Your First Kill — Reconciliation
Try ItTimed challenge — 10 min
The Task
This is the core exercise of the workshop. Every person types the exact same prompt. But because each person has a different CLAUDE.md and different department data files, every single person gets a different output tailored to their work. This is the 'Same Prompt, Different Universe' pattern.
Verification Checklist
4The CTOC Framework
Key ConceptYou just ran a six-line prompt and got a production-quality workbook
5 min
The CTOC Framework
Key ConceptYou just ran a six-line prompt and got a production-quality workbook
The CTOC Framework
5 minYou just ran a six-line prompt and got a production-quality workbook. But why did it work? Most people treat prompt writing like wish-making — throw words at the screen and hope for the best. CTOC turns prompt writing into a repeatable method.
5Where Cowork Fits
LearnQuick orientation
5 min
Where Cowork Fits
LearnQuick orientation
Where Cowork Fits
5 minQuick orientation. Claude comes in three forms. You need to know which one you are using and why.
6Traffic Light Verification
Cowork is impressive
5 min
Traffic Light Verification
Cowork is impressive
Traffic Light Verification
5 minCowork is impressive. It produces outputs that look professional, read confidently, and arrive fast. That is exactly what makes it dangerous. A polished-looking output with a wrong number is worse than no output at all — because you trust it.
7Monday Promise
You have a working CLAUDE.md, a verified reconciliation workbook, and the CTOC framework
5 min
Monday Promise
You have a working CLAUDE.md, a verified reconciliation workbook, and the CTOC framework
Monday Promise
5 minYou have a working CLAUDE.md, a verified reconciliation workbook, and the CTOC framework. Now comes the commitment. Write down one specific task you will automate next Monday. Not 'use AI more.' A specific task, a specific day, a specific time.
8Buffer
Quick checks, troubleshooting, and a preview of what comes next.
3 min
Buffer
Quick checks, troubleshooting, and a preview of what comes next.
Buffer
3 minQuick checks, troubleshooting, and a preview of what comes next.
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.
Two-Source Reconciliation
Scheme Outcomes vs Case Tracker
Bank Settlement vs Internal Ledger
Pipeline Deals vs CRM Records
Ticket Volumes vs Staffing Levels
Screening Export vs Internal Notes
HR Records vs On-Call Schedule
Application Tracker vs CDD Status
Key Takeaways
Create a personalised CLAUDE.md identity file that tells Cowork who you are, what tools you use, and what rules to follow
Run a universal reconciliation prompt against your department's data and produce a verified Excel workbook
Apply the CTOC prompt framework to understand why good prompts work and bad prompts fail
The security perimeter for Cowork is the folder you granted access to. Inside that folder, Cowork can read, write, create, delete, and modify anything. Outside it, Cowork cannot touch your files.
Rules that apply from this workshop forward:
- Never grant Cowork access to folders containing PCI data (card numbers, CVVs)
- Never drop unredacted KYC documents (passports, ID scans, proof of address) into the workspace
- Never grant access to cloud-synced directories (OneDrive, Dropbox) — Cowork could modify files that sync to shared drives
- Never grant access to your home folder, Desktop, Documents, or Downloads
- Always use a dedicated, isolated workspace folder
- Always verify outputs before forwarding, publishing, or acting on them
- Always treat Cowork's output as a draft that requires human sign-off
safety: We handle payment data, merchant PII, and regulated financial information. The "always verify, never auto-publish" rule is not a nice-to-have — it is a compliance requirement. Every workshop includes a verification step. Skipping it is not an option.
All example data in this workshop uses fictional merchants, employees, and transactions. No real payment data, merchant identifiers, or personal information is used in any exercise.
Materials
Download these files to use with the exercises above. Previews load automatically.