Claude Capabilities Workshop

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

5 min

What Claude is / what it isn't

5 min

How your team can use it every day + connectors

8 min

How to talk to Claude — with before/after demo DEMO

5 min

Projects — with interactive demo DEMO

5 min

Skills — with skill-building demo DEMO

5 min

MCPs & APIs — with cross-system demo DEMO

5 min

Cowork + Agents — with live demos DEMO

Part 2 — Where It Fits at NXT

10 min

NXT today, integration map, architecture

5 min

Your NXT formatting skill preview

Part 3 — Q&A

30 min

Questions, discussion, what would help most

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.

What Claude Is / What It Isn't

Common misconceptions — especially if you've used ChatGPT or Google Bard before

What it is

✓

A reasoning engine

It reads, analyses, synthesises, and writes. Think of it as a very fast, very thorough colleague who never gets tired.

✓

As good as what you give it

Claude reasons from the context you provide. Upload your docs, paste your data, explain the situation — and it gets dramatically better.

✓

A tool you direct

You're the scientist. Claude is the assistant. It drafts, you decide. It proposes, you validate. Always review the output.

✓

Private to your team

On Claude Team plan, your conversations and data are not used to train models. Your knowledge stays yours.

What it isn't

✗

Not a search engine

Don't use it to look up phone numbers or live stock prices. It reasons from knowledge and docs you provide — not by crawling the web in real time.

✗

Not infallible

It can sound confident and be wrong. Always verify critical facts, especially numbers, citations, and scientific claims. Trust but verify.

✗

Not remembering you (by default)

Each new conversation starts fresh — unless you use Projects, which persist knowledge and instructions across all chats.

✗

Not replacing your judgment

It's a power tool, not autopilot. Your expertise in tissue culture, genetics, and operations is what makes the output valuable.

How Your Team Can Use Claude Every Day

Before we get into the advanced capabilities — here's what you can do right now, today

✍️

Writing & Drafting

Draft client emails and responses
Write position descriptions
Create meeting agendas
Turn rough notes into a polished brief
Rewrite text for different audiences
"Make this more formal for the board"

📊

Analysis & Research

Summarise a long document or paper
Compare two approaches side by side
Analyse data you paste in or upload
"What are the key risks in this plan?"
Literature reviews and background research
"Summarise this PDF in 5 bullet points"

📁

Documents & Formatting

Generate Word docs, spreadsheets, slides
Reformat existing documents to brand standards
Build templates you can reuse
Create tables, charts, summaries
"Turn these notes into a one-page report with the NXT formatting"

💡 Pro tip: You don't need any special setup for these. Just go to claude.ai and start typing. The more context you give, the better the output.

Connectors You Can Use Right Now

Claude can connect to the tools you already use — enable them in Settings → Connectors

📧

Gmail

"Draft a reply to Daniel's email about the board paper." "Find the last email from the logistics company." "Write a follow-up to Kylie about the SOP templates."

📅

Google Calendar

"What's on my schedule tomorrow?" "Find a free slot next week for a 30-minute catch-up." "When is my next meeting with the research team?"

📂

Google Drive

"Find the Q2 production report in my Drive." "Summarise the latest board paper draft." "Search for any documents about contamination protocols."

💡 How to enable connectors

1. Go to claude.ai → Settings → Connectors
2. Click "Connect" next to Gmail, Google Calendar, or Google Drive
3. Authorise access
4. Done — Claude can now read and search these in any conversation

These are separate from MCPs (which we'll cover later). Connectors are built-in, zero setup, and ready to go.

🔒 Privacy note

Claude only accesses your connected services when you ask it to in a conversation. It doesn't passively read your inbox or calendar.

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.

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."

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."

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.

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."

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

Step 1 of 4

Claude— General Chat

Click "Next Step" to continue...

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

Step 1 of 4

Claude— General Chat (no project)

Click "Next Step" to continue...

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

Step 1 of 5

Claude— NXT Document Standards

Click "Next Step" to continue...

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.

📓

Notion

Search pages, read databases, create & update records

📋

Asana

Query tasks & projects, create actions, check blockers

📅

Calendar

Check availability, schedule meetings

📂

Drive

Access 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

Step 1 of 4

Claude— NXT Research (Notion + Asana connected)

Click "Next Step" to continue...

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

Step 1 of 4

Cowork— Task: Process meeting transcript

Click "Next Step" to continue...

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

Cowork Scheduled Tasks

Set cadence in Desktop. Runs while machine is on. Best for personal recurring work.

Cloud Agents

Run on Anthropic's servers. Machine off is fine. Best for team automations.

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

Step 1 of 4

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

Coming Soon: Your NXT Formatting Skill

A .md file that makes every document look like this — automatically

What it defines

The NXT formatting skill specifies every visual detail so Claude produces brand-consistent documents without you describing the formatting each time:

· Typography: Aptos — H1 28pt Bold, H2 20pt Bold, Body 11pt
· Colours: ■ Neon Green #00FF00 accents ■ Charcoal #54565B text ■ Soft Grey #C1C5C9 borders
· Layout: Green accent bar top, logo top-right, 1in margins
· Tables: Charcoal header, alternating white/grey rows
· Footer: "NXT Bioscience" | Page number | 9pt Charcoal

How to use it:
1. Upload nxt-brand.md to your project's knowledge base
2. Add this instruction: "Draw formatting from nxt-brand.md"
3. Every document Claude produces will follow the brand — board papers, SOPs, reports, templates

Sample Board Paper

Generated with NXT formatting skill

NXT

Summary: Production tracking 8% ahead of forecast. Two new AX protocols initiated. Contamination rate below 2% target for Q2.

Production Performance

142,000 vessels produced (forecast: 131,500). AX output +23% post-automation upgrade.

Research & Development

Two initiation protocol trials started. Media optimisation showing 12% multiplication improvement.

Metric	Q1	Q2	Δ
Vessels Produced	128K	142K	+11%
Contamination Rate	2.3%	1.8%	−0.5pp

NXT BiosciencePage 1

✓ Green bar ✓ Logo ✓ Aptos ✓ Summary box ✓ Branded table ✓ Footer

Questions &
Discussion

What would make the biggest difference for your work?

Kavan Mehta · kavan.mehta@attaliscapital.com