Claude Capabilities
Workshop
Everything you need to know — and where it fits at NXT
Kavan Mehta · 19 May 2026
Today's Session
60 minutes + 30 min open Q&A
Part 1 — Claude Fundamentals
5 min
Chat vs Code vs Cowork — three products, one AI
8 min
How to talk to Claude — with before/after demo DEMO
8 min
Projects — with interactive demo DEMO
8 min
Skills — with skill-building demo DEMO
8 min
MCPs & APIs — with cross-system demo DEMO
8 min
Cowork — with file processing demo DEMO
8 min
Agents & Automations — with briefing demo DEMO
Part 2 — Where It Fits at NXT
10 min
NXT today, integration map, architecture
5 min
How I'll help your team build the layer
Part 3 — What's Next
5+30
Things you can do today + Q&A
Part 1
Claude Fundamentals
What it is, how it works, every capability — with live demos
Claude: Three Products, One AI
Same model — the difference is what Claude can access
💬
Claude Chat
Web and mobile interface. You type, Claude responds. Upload files, search the web, connect to tools. Your daily driver for research, writing, analysis, and document creation.
⌨️
Claude Code
Command-line tool for developers. Reads codebases, writes code, runs commands, debugs. This is what's used behind the scenes for technical build work — you won't need this day to day.
🖥️
Cowork
Desktop app where Claude sees your files, opens apps, navigates your browser, completes multi-step tasks autonomously. Describe the outcome — Claude handles the execution. No coding needed.
00
How to Talk to Claude
The difference between a vague ask and a useful answer
The Five Things Claude Needs
You wouldn't brief a new employee by saying "do the thing." Same applies here.
1
Context
Who are you, what's the situation, what background does Claude need? "I'm running a tissue culture lab with 1000+ species across contract propagation and R&D."
2
Task
Exactly what you want done — specific verb. Not "help me with this project" but "break this project into 2-week milestones with deliverables for each."
3
Inputs
Give Claude the raw material. Paste the data, upload the doc, share the transcript. Claude reasons from what you give it — not from guessing.
4
Output format
Tell Claude what the result should look like. "Give me a table." "Write it as a one-page brief." "Keep it under 200 words." "Use bullet points."
5
Constraints
What to avoid, what tone, what audience. "This is for the board — no jargon." "Don't produce a final document yet — just give me the structure to review."
❌ Vague prompt
"How should I do this project?"
Claude doesn't know what project, who's involved, what success looks like, or what format you want. You'll get generic advice you can't use.
✓ Structured prompt
"I need to roll out Notion across our 12-person research team over 6 weeks. We currently use OneNote for lab notebooks and SharePoint for shared files. Break this into fortnightly phases with specific deliverables. Output as a table with columns: Phase, Dates, Tasks, Owner, Done Criteria. Keep it to one page."
Claude knows the scope, the timeline, the current state, and exactly what format to deliver.
Next slide: see both side by side →
Prompting Demo
Same task, two approaches
1Vague prompt
2Generic response
3Structured prompt
4Actionable response
Click "Next Step" to continue...
01
Projects
Persistent AI workspaces — instructions, knowledge, memory
Projects: How They Work
A Project is a persistent workspace. Everything inside it shapes every response.
✓
Instructions
Permanent rules. "Use Australian English." "Preview before producing a document." Apply to every conversation in the project.
✓
Knowledge Docs
Upload PDFs, Word docs, spreadsheets. Claude reads them before answering — reasons from your data, not the internet.
✓
Memory
Claude remembers facts and preferences across conversations. Learns your terminology and shorthand.
✓
Conversations
Multiple threads in one project. A thread per trial, per report, per workstream — all sharing the same knowledge.
💡 Key insight
Context quality = output quality. The same prompt gives completely different results depending on what knowledge docs are attached. Without them, Claude guesses from the internet. With them, it reasons from NXT's actual data.
Next slide: see this in action →
Projects Demo
Generic vs knowledge-grounded
1Ask without knowledge
2See generic response
3Same question, with docs
4See grounded response
Claude— General Chat (no project)
Click "Next Step" to continue...
02
Skills
Structured instruction files — specifications, not suggestions
Skills: Instructions vs Specifications
A Skill is a .md file that defines exactly how Claude performs a task.
Instruction (what you've been doing)
"Use the brand template. Make it professional."
⚠ Variable results — logo wrong, colours off, fonts different
Skill (specification)
"H1: Aptos 28pt #000. Logo: top-right 1.2in. Bar: #00FF00 3px."
✓ Consistent branded output — every single time
Deploy across NXT: build once → store in Notion → everyone uploads to their projects. On Team plan, org-level cascade. Next slide: watch one being built →
Skills Demo
Building a formatting skill from scratch
1Define requirements
2Claude builds the skill
3Test on a document
4See the result
5Export and deploy
Claude— NXT Document Standards
Click "Next Step" to continue...
03
MCPs & APIs
How Claude connects to external systems — live, in your conversation
MCPs: Claude's Live Connectors
MCP = Model Context Protocol. A plug that lets Claude read and write to external systems. No copy-paste.
📓NotionSearch pages, read databases, create & update records
📋AsanaQuery tasks & projects, create actions, check blockers
📅CalendarCheck availability, schedule meetings
📂DriveAccess shared docs, spreadsheets, files
APIs: The Developer Layer
MCPs are user-facing — everyone on the team enables them and queries through Claude Chat.
APIs are developer-facing — code that calls Claude programmatically. This is how automated pipelines get built: a script pulls data from Asana's API, sends it to Claude's API, and delivers a report. Nobody touched a keyboard.
Next slide: see a cross-system query in action →
MCPs Demo
Cross-system query: Notion + Asana
1Ask a cross-system question
2Claude queries Notion
3Claude queries Asana
4Synthesised answer
Claude— NXT Research (Notion + Asana connected)
Click "Next Step" to continue...
04
Cowork
Claude on your desktop — files, apps, scheduled tasks
Cowork: What It Can Do
A mode in Claude Desktop. Claude has direct access to your files and can work independently.
📁
File Operations
Organise, rename, sort, deduplicate. Point at a folder and describe what you want — Claude handles it.
📝
Document Work
Read multiple source docs, synthesise, format, produce polished outputs. No copy-paste needed.
⏰
Scheduled Tasks
Set a cadence: daily, weekly, monthly. Claude runs automatically. Weekly summaries, Friday reports, quarterly reviews.
Next slide: watch Cowork process meeting transcripts →
Cowork Demo
Processing a Teams meeting transcript
1Point at transcript file
2Claude reads the file
3Extracts decisions & actions
4Saves structured output
Cowork— Task: Process meeting transcript
Click "Next Step" to continue...
05
Agents &
Automations
Work that runs without you — scheduled, triggered, autonomous
Agents & Automations
An agent runs on a schedule. An automation triggers on an event. Both remove manual work.
Three ways to automate
1
Cowork Scheduled Tasks
Set cadence in Desktop. Runs while machine is on. Best for personal recurring work.
2
Cloud Agents
Run on Anthropic's servers. Machine off is fine. Best for team automations.
3
n8n / Make Orchestration
Connect multiple systems. Best for complex multi-step pipelines.
The pattern
Trigger (schedule or event) → Capture (data flows in) → Reason (Claude analyses) → Act (output delivered)
Next slide: see a CEO briefing agent run →
Agent Demo
Weekly CEO briefing — automated
1Monday 7am trigger
2Pull Asana data
3Pull Notion updates
4Deliver CEO briefing
Agent— Weekly CEO Briefing (Scheduled: Mon 7:00 AM)
Click "Next Step" to continue...
Part 2
Where It Fits at NXT
Mapping Claude to your actual operations
NXT Today
Plant tissue culture, automated propagation, bioreactors, live research — across 1000+ species
Your systems
- POTS — production planning, forecasting, orders, lab floor data capture
- OneNote — lab notebooks, research observations, trial notes
- Asana — project tasks, sprint planning, team coordination
- Teams — meetings, daily comms, decisions made verbally
- Notion — knowledge hub being built (research repo + business system)
- SharePoint — shared files, documents, templates
Where knowledge gets lost
- Media formulation expertise lives in senior scientists' heads
- AX protocol development knowledge doesn't compound across trials
- Decisions from Tuesday's meeting are in an unread transcript
- Trial results stay in individual notebooks — no cross-referencing
- Every board paper comes out with different formatting
- Genetic banking records across scattered spreadsheets
Claude × NXT Operations
| Operation | Today | With Claude | Uses |
|---|
| Contract Propagation | Order volumes and delivery schedules in POTS. Client comms manual. | Order risk alerts, capacity cross-referencing, client status reports on demand. | MCPProject |
| R&D / AX Protocols | Scientists design trials from memory. Results in individual notebooks. | Project with NXT knowledge docs. Trials grounded in actual data. Cross-trial synthesis. | ProjectDocs |
| Genetic Banking | Germplasm records across spreadsheets. 1000+ species tracked manually. | Notion-connected knowledge base. Species queries, provenance tracking, genetic certificates. | MCPSkill |
| Lab Quality | Contamination recorded but not analysed. Patterns invisible. | Cross-reference events against batches, rooms, time. Identify systemic issues early. | AutoMCP |
| Leadership | Board papers manual. No automated project visibility. | CEO briefing agent. Formatting skill for brand consistency. Reports from live data. | AgentSkill |
| Meetings | Decisions verbal. Transcripts unread. Actions lost. | Transcript → Claude → decisions + actions extracted → Notion + Asana automatically. | AutoMCP |
| Mine Site Restoration | Endemic records and planting plans in scattered docs. | Project with site ecology docs. Species management, compliance reports, biodiversity tracking. | ProjectSkill |
The NXT Intelligence Layer
Claude above your systems as the reasoning layer — scientist in the loop
Intelligence Layer
Claude — reasoning, synthesis, generation, scheduling
▼
Knowledge Hub
Notion — research library, SOPs, genetic records, business system
▼
Data Integration
MCPs + APIs + automations
▼
Systems of Execution
POTS · Asana · Teams · SharePoint · Lab · Bioreactors
Questions &
Discussion
What would make the biggest difference for your work?
Kavan Mehta · kavan.mehta@attaliscapital.com