Antuko in-company session. The basics, plus the three automations we build live — every prompt ready to copy.
🤖 The shift today: Claude doesn't just answer — with connectors it acts. Reports, searches, minutes — done for you.
Start here · talking to Claude
A good prompt = role + context + goal + output format. That single habit is most of the value.
Weak vs strong prompt
You are a project-finance analyst at a renewables developer. I'll paste raw weekly energy prices. Summarise the trend in 3 bullets, flag anything unusual, and give me a one-line takeaway for the team. Output as Markdown.
Never paste: IBAN, counterparty bank data, tax IDs, individual salaries. Anonymise first. Claude proposes — you verify.
Demo 1 · Energy price agent
Pull Polish power-market prices (PSE), turn them into a report, draft the team email. Weekly, unattended.
Prompt
Get the PSE RCE prices for the last full week and write a short report on the trend (min / max / average per day) with a one-paragraph comment. Then draft a team email with that summary.
PSE publishes with a lag → ask for a range ending 2–3 days ago. This becomes a scheduled weekly routine.
Demo 2 · Find answers in the team's files
Someone who knows nothing about a topic finds concrete answers inside the shared repository — with the source.
Prompt
I know nothing about environmental permits in Chile. Search our shared folder and tell me what permits are required, the key deadlines, and which document each answer comes from.
Searches by content, not file name. Always cites the source document — check against the original. (Pattern shown on Drive; your SharePoint equivalent works the same way.)
Demo 3 · Automatic meeting minutes
From raw notes to an actionable minute — sent to participants, stored, and searchable later.
Prompt
Turn these meeting notes into minutes with four sections: key points discussed, agreements, owners, next steps. Keep it tight. Then draft an email to the participants with the minutes, and tell me how to file it so it's searchable later.
Same structure every time → easy to index and ask later: "what did we agree about X in May?"
Limits & security
What Claude must NOT do: final deliverables without review · critical arithmetic unverified · tax/legal advice · process files of unknown origin (prompt-injection risk). RGPD/AI Act: check what can go into a connector with your DPO/lawyer.
What you take home
A solid habit for talking to Claude + one strong prompt of your own.
The three automations seen live: price agent · repository search · meeting minutes.
A pattern you can take to your own SharePoint / Dropbox.
Limits/security capsule + a 30-day adoption roadmap.