Don't start from a blank prompt. Copy a ready-made skill, paste it into your chat with Brain, and it's yours — trigger it any time with a slash command.
How it works
Browse by category; tap a skill’s "View" to see exactly what it does.
Copy a skill and paste it into your chat with Brain (Slack, Google Chat or Teams).
Brain runs a quick safety check, saves it, and confirms — then trigger it any time with its command.
Email & your day
/inbox-triage
Inbox Triage
Scan your inbox, surface the few emails that actually need you, and draft replies
---
name: inbox-triage
description: Scan your inbox, surface the few emails that actually need you, and draft replies
trigger: /inbox-triage
user_invocable: true
---
# Inbox Triage
Go through recent mail, separate signal from noise, and prepare draft replies so you only spend time on what matters.
## Workflow
1. Read the unread and recent messages in the connected mailbox (Gmail or Outlook).
2. Group them into: **Needs a reply from you**, **FYI / no action**, and **Newsletters & automated**.
3. For each "Needs a reply", write a one-line summary (who, what they want, any deadline) and a **draft reply** in the user's voice. Leave the drafts for review — do not send.
4. Post a short digest in chat: the 3–6 items that need attention, each with its one-line summary and the draft ready to approve.
## Notes
- Mail is draft-only; never send without the user's explicit approval.
- Keep it short — the goal is to surface the handful that need a human, not summarise everything.
- To run this automatically every morning, say: "run /inbox-triage every weekday at 8am".
Go through recent mail, separate signal from noise, and prepare draft replies so you only spend time on what matters.
## Workflow
1. Read the unread and recent messages in the connected mailbox (Gmail or Outlook).
2. Group them into: **Needs a reply from you**, **FYI / no action**, and **Newsletters & automated**.
3. For each "Needs a reply", write a one-line summary (who, what they want, any deadline) and a **draft reply** in the user's voice. Leave the drafts for review — do not send.
4. Post a short digest in chat: the 3–6 items that need attention, each with its one-line summary and the draft ready to approve.
## Notes
- Mail is draft-only; never send without the user's explicit approval.
- Keep it short — the goal is to surface the handful that need a human, not summarise everything.
- To run this automatically every morning, say: "run /inbox-triage every weekday at 8am".
/weekly-digest
Weekly Digest
A Monday-morning digest of your week — calendar, open threads, and what needs attention
---
name: weekly-digest
description: A Monday-morning digest of your week — calendar, open threads, and what needs attention
trigger: /weekly-digest
user_invocable: true
---
# Weekly Digest
Start the week with one clear picture: what's on the calendar, which conversations are still open, and what needs a decision.
## Workflow
1. Read this week's calendar events from the connected account.
2. Scan recent mail for threads still awaiting a reply or a decision.
3. If a task tool is connected (Trello, HubSpot tasks), pull anything due this week.
4. Produce a digest:
- **This week's meetings** — day, time, who, one-line purpose
- **Open threads** — conversations that need your reply
- **Due this week** — tasks and deadlines
- **Suggested focus** — the 3 things most worth your time
5. Post it in chat.
## Notes
- Read-only summary; it does not change anything.
- To get it every Monday, say: "run /weekly-digest every Monday at 8am".
Start the week with one clear picture: what's on the calendar, which conversations are still open, and what needs a decision.
## Workflow
1. Read this week's calendar events from the connected account.
2. Scan recent mail for threads still awaiting a reply or a decision.
3. If a task tool is connected (Trello, HubSpot tasks), pull anything due this week.
4. Produce a digest:
- **This week's meetings** — day, time, who, one-line purpose
- **Open threads** — conversations that need your reply
- **Due this week** — tasks and deadlines
- **Suggested focus** — the 3 things most worth your time
5. Post it in chat.
## Notes
- Read-only summary; it does not change anything.
- To get it every Monday, say: "run /weekly-digest every Monday at 8am".
/eod
End of Day
An end-of-day wrap — what got done, what slipped, and tomorrow's setup
---
name: end-of-day
description: An end-of-day wrap — what got done, what slipped, and tomorrow's setup
trigger: /eod
user_invocable: true
---
# End of Day
Wind down with a clear picture: what you closed today, what's still open, and what tomorrow needs.
## Workflow
1. Scan today's calendar and recent mail for what happened and what's still waiting on you.
2. Check tomorrow's calendar for the first meetings and anything to prepare tonight.
3. Produce a short wrap:
- **Done today** — the notable items
- **Still open** — what slipped or needs a reply
- **Tomorrow** — first meetings plus anything to prep
4. Post it in chat.
## Notes
- Keep it brief — a 30-second read to close the day.
- To get it every weekday evening, say: "run /eod every weekday at 6pm".
Wind down with a clear picture: what you closed today, what's still open, and what tomorrow needs.
## Workflow
1. Scan today's calendar and recent mail for what happened and what's still waiting on you.
2. Check tomorrow's calendar for the first meetings and anything to prepare tonight.
3. Produce a short wrap:
- **Done today** — the notable items
- **Still open** — what slipped or needs a reply
- **Tomorrow** — first meetings plus anything to prep
4. Post it in chat.
## Notes
- Keep it brief — a 30-second read to close the day.
- To get it every weekday evening, say: "run /eod every weekday at 6pm".
/follow-ups
Follow-up Tracker
Track who you're waiting on and who's waiting on you, and draft nudges
---
name: follow-up-tracker
description: Track who you're waiting on and who's waiting on you, and draft nudges
trigger: /follow-ups
user_invocable: true
---
# Follow-up Tracker
Never drop a thread: see who owes you a reply, who you owe one, and get gentle nudges drafted.
## Workflow
1. Scan recent sent and received mail for threads where a reply is expected but hasn't come.
2. Split into **They owe you** (you sent, no reply after several days) and **You owe them** (they're waiting on you).
3. For the "they owe you" items, draft a short, polite follow-up nudge for each.
4. Post a list in chat: each open thread, who it's with, how long it's been waiting, and the draft nudge ready to send after approval.
## Notes
- Nudge emails are drafts — never sent without approval.
- To run it twice a week, say: "run /follow-ups every Tuesday and Friday at 9am".
Never drop a thread: see who owes you a reply, who you owe one, and get gentle nudges drafted.
## Workflow
1. Scan recent sent and received mail for threads where a reply is expected but hasn't come.
2. Split into **They owe you** (you sent, no reply after several days) and **You owe them** (they're waiting on you).
3. For the "they owe you" items, draft a short, polite follow-up nudge for each.
4. Post a list in chat: each open thread, who it's with, how long it's been waiting, and the draft nudge ready to send after approval.
## Notes
- Nudge emails are drafts — never sent without approval.
- To run it twice a week, say: "run /follow-ups every Tuesday and Friday at 9am".
/morning-brief
Morning Brief
One morning message — today's calendar, the emails that need you, and your tasks
---
name: morning-brief
description: One morning message — today's calendar, the emails that need you, and your tasks
trigger: /morning-brief
user_invocable: true
---
# Morning Brief
Start the day with one clear message: what's ahead, what needs you, and what to focus on.
## Workflow
1. Read today's calendar events from the connected account.
2. Scan recent mail for anything that needs a reply or a decision today.
3. If task tools are connected (Trello, HubSpot), pull what's due today.
4. Produce a short brief:
- **Today's schedule** — meetings with time and purpose
- **Needs you** — emails or decisions to handle
- **Due today** — tasks and deadlines
- **Focus** — the 2–3 things most worth your time
5. Post it in chat.
## Notes
- Read-only summary; it changes nothing.
- To get it every weekday morning, say: "run /morning-brief every weekday at 7am".
Start the day with one clear message: what's ahead, what needs you, and what to focus on.
## Workflow
1. Read today's calendar events from the connected account.
2. Scan recent mail for anything that needs a reply or a decision today.
3. If task tools are connected (Trello, HubSpot), pull what's due today.
4. Produce a short brief:
- **Today's schedule** — meetings with time and purpose
- **Needs you** — emails or decisions to handle
- **Due today** — tasks and deadlines
- **Focus** — the 2–3 things most worth your time
5. Post it in chat.
## Notes
- Read-only summary; it changes nothing.
- To get it every weekday morning, say: "run /morning-brief every weekday at 7am".
Content & social
/social
Social Post
Draft ready-to-publish social posts (LinkedIn, X) from a topic, link, or update
---
name: social-post
description: Draft ready-to-publish social posts (LinkedIn, X) from a topic, link, or update
trigger: /social
user_invocable: true
---
# Social Post
Turn an idea, a link, or a piece of news into polished social posts you can copy and publish — in your voice.
## Parameters
- **topic / source** (required) — what to post about: a topic, a pasted article or link, a product update, or a recent win.
- **platforms** (optional) — LinkedIn, X, or both. Defaults to LinkedIn.
## Workflow
1. Understand the source: read the pasted text, or if a link is given, summarise its key point.
2. Draft posts tailored per platform — a longer professional take for LinkedIn, a tight punchy version for X. Offer 2–3 variations to choose from.
3. Add a few relevant hashtags and a clear call to action where it fits.
4. Reply in chat with the drafts, ready to copy and publish.
## Notes
- Drafts only — Brain doesn't post to social networks; you copy the one you like and publish it.
- Match the user's tone (check past posts if available); avoid hype and keep claims honest.
Turn an idea, a link, or a piece of news into polished social posts you can copy and publish — in your voice.
## Parameters
- **topic / source** (required) — what to post about: a topic, a pasted article or link, a product update, or a recent win.
- **platforms** (optional) — LinkedIn, X, or both. Defaults to LinkedIn.
## Workflow
1. Understand the source: read the pasted text, or if a link is given, summarise its key point.
2. Draft posts tailored per platform — a longer professional take for LinkedIn, a tight punchy version for X. Offer 2–3 variations to choose from.
3. Add a few relevant hashtags and a clear call to action where it fits.
4. Reply in chat with the drafts, ready to copy and publish.
## Notes
- Drafts only — Brain doesn't post to social networks; you copy the one you like and publish it.
- Match the user's tone (check past posts if available); avoid hype and keep claims honest.
/blog
Blog Draft
Draft a blog post from a topic or rough outline
---
name: blog-draft
description: Draft a blog post from a topic or rough outline
trigger: /blog
user_invocable: true
---
# Blog Draft
Go from a topic or a few bullet points to a structured first-draft blog post — ready to edit and publish.
## Parameters
- **topic / outline** (required) — the subject, angle, and any points to cover.
- **length** (optional) — short (~600 words) or standard (~1000–1200). Defaults to standard.
## Workflow
1. Clarify the angle and audience if needed.
2. If research helps, search the web for supporting facts and name the sources.
3. Draft the post: a hook, 3–5 sections with subheadings, and a short conclusion with a call to action.
4. Save it as a document (Word or Google Docs) if asked, and post the draft in chat.
## Notes
- A first draft to edit — check facts and add your own voice before publishing.
- Keep claims grounded; flag anything you weren't sure about.
Go from a topic or a few bullet points to a structured first-draft blog post — ready to edit and publish.
## Parameters
- **topic / outline** (required) — the subject, angle, and any points to cover.
- **length** (optional) — short (~600 words) or standard (~1000–1200). Defaults to standard.
## Workflow
1. Clarify the angle and audience if needed.
2. If research helps, search the web for supporting facts and name the sources.
3. Draft the post: a hook, 3–5 sections with subheadings, and a short conclusion with a call to action.
4. Save it as a document (Word or Google Docs) if asked, and post the draft in chat.
## Notes
- A first draft to edit — check facts and add your own voice before publishing.
- Keep claims grounded; flag anything you weren't sure about.
/newsletter
Newsletter Draft
Draft an email newsletter or update from your recent news and links
---
name: newsletter-draft
description: Draft an email newsletter or update from your recent news and links
trigger: /newsletter
user_invocable: true
---
# Newsletter Draft
Pull your recent updates into a clean newsletter draft — intro, a few items, and a sign-off.
## Parameters
- **theme / items** (required) — what this issue is about, plus any links or notes to include.
## Workflow
1. Gather the material: the items the user provides, plus relevant recent wins from mail or files if asked.
2. Draft the newsletter: a short intro, 3–6 items each with a heading and a couple of lines, and a sign-off.
3. Keep a consistent, friendly tone and suggest a subject line.
4. Save it as a document or an email draft (never sent) and post it in chat for review.
## Notes
- Email drafts are never sent automatically — you review and send.
- Suggest 2–3 subject-line options.
Pull your recent updates into a clean newsletter draft — intro, a few items, and a sign-off.
## Parameters
- **theme / items** (required) — what this issue is about, plus any links or notes to include.
## Workflow
1. Gather the material: the items the user provides, plus relevant recent wins from mail or files if asked.
2. Draft the newsletter: a short intro, 3–6 items each with a heading and a couple of lines, and a sign-off.
3. Keep a consistent, friendly tone and suggest a subject line.
4. Save it as a document or an email draft (never sent) and post it in chat for review.
## Notes
- Email drafts are never sent automatically — you review and send.
- Suggest 2–3 subject-line options.
/repurpose
Content Repurpose
Turn one piece of content into social posts, an email, and a summary
---
name: content-repurpose
description: Turn one piece of content into social posts, an email, and a summary
trigger: /repurpose
user_invocable: true
---
# Content Repurpose
One blog post or document becomes a week of content — social posts, a short email, and a summary, all in your voice.
## Parameters
- **source** (required) — the content to repurpose: paste it, name a file in your Drive, or give a link.
## Workflow
1. Read the source and pull out the core message and 3–5 key points.
2. Produce a set:
- a **LinkedIn post** and a shorter **X post**
- a **short email** version for a newsletter
- a **one-paragraph summary**
3. Keep each tailored to its format and to the user's tone.
4. Post the set in chat, ready to copy.
## Notes
- Drafts to review and publish yourself.
- Don't add claims that aren't in the source.
One blog post or document becomes a week of content — social posts, a short email, and a summary, all in your voice.
## Parameters
- **source** (required) — the content to repurpose: paste it, name a file in your Drive, or give a link.
## Workflow
1. Read the source and pull out the core message and 3–5 key points.
2. Produce a set:
- a **LinkedIn post** and a shorter **X post**
- a **short email** version for a newsletter
- a **one-paragraph summary**
3. Keep each tailored to its format and to the user's tone.
4. Post the set in chat, ready to copy.
## Notes
- Drafts to review and publish yourself.
- Don't add claims that aren't in the source.
Documents
/report
Report Builder
Turn a short brief and your data into a clean Word or Google Docs report
---
name: report-builder
description: Turn a short brief and your data into a clean Word or Google Docs report
trigger: /report
user_invocable: true
---
# Report Builder
Go from a one-line brief to a structured, branded report document — a first draft ready to review.
## Parameters
- **brief** (required) — what the report is about and who it's for.
- **period / data** (optional) — the timeframe or source (calendar, a spreadsheet, recent emails).
## Workflow
1. Clarify the brief if needed: audience, period, and which sections matter.
2. Gather the inputs — pull figures from a named spreadsheet, events from the calendar, or notes from recent mail.
3. Draft a structured report (Word in OneDrive, or Google Docs in Google Drive): title, summary, the main sections, and a short conclusion. Apply the user's template or brand if one is in their Drive.
4. Save it and reply with the file name, noting it's a first draft to review and refine.
## Notes
- Present it as a first draft — check the figures before sharing.
- Keep every claim grounded in the provided data; do not invent numbers.
Go from a one-line brief to a structured, branded report document — a first draft ready to review.
## Parameters
- **brief** (required) — what the report is about and who it's for.
- **period / data** (optional) — the timeframe or source (calendar, a spreadsheet, recent emails).
## Workflow
1. Clarify the brief if needed: audience, period, and which sections matter.
2. Gather the inputs — pull figures from a named spreadsheet, events from the calendar, or notes from recent mail.
3. Draft a structured report (Word in OneDrive, or Google Docs in Google Drive): title, summary, the main sections, and a short conclusion. Apply the user's template or brand if one is in their Drive.
4. Save it and reply with the file name, noting it's a first draft to review and refine.
## Notes
- Present it as a first draft — check the figures before sharing.
- Keep every claim grounded in the provided data; do not invent numbers.
/proposal
Proposal Draft
Draft a client proposal or quote document from a few details
---
name: proposal-draft
description: Draft a client proposal or quote document from a few details
trigger: /proposal
user_invocable: true
---
# Proposal Draft
Turn a few details into a clean proposal document — scope, deliverables, pricing — ready for you to review and send.
## Parameters
- **client & scope** (required) — who it's for and what you're proposing.
- **pricing** (optional) — amounts or a rate; Brain asks if it's missing.
## Workflow
1. Collect the essentials: client, problem, proposed scope, deliverables, timeline, and pricing.
2. If the client already exists in your connected CRM, pull their company details for the header.
3. Draft a proposal document (Word in OneDrive, or Google Docs in Google Drive) on the user's template or brand if available: cover, context, scope, deliverables, timeline, pricing, next steps.
4. Save it and reply with the file name, noting it's a draft to review before sending.
## Notes
- Draft only — never send to the client without explicit approval.
- Leave clearly marked placeholders for anything you had to guess.
Turn a few details into a clean proposal document — scope, deliverables, pricing — ready for you to review and send.
## Parameters
- **client & scope** (required) — who it's for and what you're proposing.
- **pricing** (optional) — amounts or a rate; Brain asks if it's missing.
## Workflow
1. Collect the essentials: client, problem, proposed scope, deliverables, timeline, and pricing.
2. If the client already exists in your connected CRM, pull their company details for the header.
3. Draft a proposal document (Word in OneDrive, or Google Docs in Google Drive) on the user's template or brand if available: cover, context, scope, deliverables, timeline, pricing, next steps.
4. Save it and reply with the file name, noting it's a draft to review before sending.
## Notes
- Draft only — never send to the client without explicit approval.
- Leave clearly marked placeholders for anything you had to guess.
/recap
Meeting Recap
Turn raw meeting notes or a transcript into a clean recap document
---
name: meeting-recap
description: Turn raw meeting notes or a transcript into a clean recap document
trigger: /recap
user_invocable: true
---
# Meeting Recap
Drop in messy notes or a transcript and get a clean recap — decisions, action items, owners — as a document you can share.
## Parameters
- **notes** (required) — paste the notes, or attach a transcript or audio file.
## Workflow
1. Read the notes. If an audio file is attached, transcribe it first.
2. Structure a recap: attendees, key points, **decisions**, and **action items** with an owner and due date where stated.
3. Save it as a document (Word in OneDrive, or Google Docs in Google Drive) and, if asked, draft a follow-up email to attendees with the summary.
4. Reply in chat with the file name and the action-item list.
## Notes
- Any follow-up email is a draft for review — never sent automatically.
- Do not invent decisions or owners that aren't in the notes; mark gaps as "to confirm".
Drop in messy notes or a transcript and get a clean recap — decisions, action items, owners — as a document you can share.
## Parameters
- **notes** (required) — paste the notes, or attach a transcript or audio file.
## Workflow
1. Read the notes. If an audio file is attached, transcribe it first.
2. Structure a recap: attendees, key points, **decisions**, and **action items** with an owner and due date where stated.
3. Save it as a document (Word in OneDrive, or Google Docs in Google Drive) and, if asked, draft a follow-up email to attendees with the summary.
4. Reply in chat with the file name and the action-item list.
## Notes
- Any follow-up email is a draft for review — never sent automatically.
- Do not invent decisions or owners that aren't in the notes; mark gaps as "to confirm".
/doc-summary
Document Summary
Turn a long document or PDF into key points and decisions
---
name: doc-summary
description: Turn a long document or PDF into key points and decisions
trigger: /doc-summary
user_invocable: true
---
# Document Summary
Get the essence of a long document without reading all of it.
## Parameters
- **document** (required) — the Google Doc, Word / OneDrive file, PDF, or pasted text.
## Workflow
1. Read the document the user names.
2. Pull out the essentials: the main points, any decisions or conclusions, open questions, and action items.
3. Produce a summary:
- **In one line** — what the document is about
- **Key points** — the 5–8 that matter
- **Decisions / actions** — anything to do or decide
4. Post it in chat; save it as a note or document if asked.
## Notes
- Read-only; it summarises, it changes nothing.
- Keep it faithful — flag anything ambiguous rather than guessing.
Get the essence of a long document without reading all of it.
## Parameters
- **document** (required) — the Google Doc, Word / OneDrive file, PDF, or pasted text.
## Workflow
1. Read the document the user names.
2. Pull out the essentials: the main points, any decisions or conclusions, open questions, and action items.
3. Produce a summary:
- **In one line** — what the document is about
- **Key points** — the 5–8 that matter
- **Decisions / actions** — anything to do or decide
4. Post it in chat; save it as a note or document if asked.
## Notes
- Read-only; it summarises, it changes nothing.
- Keep it faithful — flag anything ambiguous rather than guessing.
/contract-review
Contract Review
Flag key terms, dates, and obligations in a contract — a first-pass read
---
name: contract-review
description: Flag key terms, dates, and obligations in a contract — a first-pass read
trigger: /contract-review
user_invocable: true
---
# Contract Review
A fast first-pass read of a contract that surfaces what matters before a human review.
## Parameters
- **document** (required) — the contract as a Google Doc, Word / OneDrive file, PDF, or pasted text.
## Workflow
1. Read the contract the user names.
2. Extract and list the key elements: parties, term and renewal, payment terms and amounts, termination and notice periods, liability and indemnity, confidentiality, and any deadlines or auto-renewal dates.
3. Flag anything unusual, one-sided, or missing that's worth a closer look.
4. Post a structured summary in chat with the clauses grouped and the dates called out.
## Notes
- A first-pass aid, **not legal advice** — have a qualified person review before signing.
- Read-only; it never edits or signs anything.
A fast first-pass read of a contract that surfaces what matters before a human review.
## Parameters
- **document** (required) — the contract as a Google Doc, Word / OneDrive file, PDF, or pasted text.
## Workflow
1. Read the contract the user names.
2. Extract and list the key elements: parties, term and renewal, payment terms and amounts, termination and notice periods, liability and indemnity, confidentiality, and any deadlines or auto-renewal dates.
3. Flag anything unusual, one-sided, or missing that's worth a closer look.
4. Post a structured summary in chat with the clauses grouped and the dates called out.
## Notes
- A first-pass aid, **not legal advice** — have a qualified person review before signing.
- Read-only; it never edits or signs anything.
Presentations
/pitch-deck
Pitch Deck
Turn a brief or one-pager into an investor or sales pitch deck
---
name: pitch-deck
description: Turn a brief or one-pager into an investor or sales pitch deck
trigger: /pitch-deck
user_invocable: true
---
# Pitch Deck
Go from a short brief to a structured pitch deck — a PowerPoint in your OneDrive, or a Google Slides deck if you're on Google.
## Parameters
- **source** (required) — the brief, one-pager, or notes to build from.
- **slides** (optional) — target slide count. Defaults to ~10.
## Workflow
1. Read the source material (pasted text, or a Doc / Word / PDF the user names).
2. Structure a standard pitch flow: problem, solution, market, product, business model, traction, team, and the ask. Skip sections the source can't support rather than inventing facts.
3. Write one clear idea per slide — a short title and 2–4 tight bullets.
4. Create the deck in the user's ecosystem: a PowerPoint (.pptx) in OneDrive or Drive, or a native Google Slides deck. Return a clickable link.
5. Post a one-line summary and the link in chat.
## Notes
- A first draft to refine — check every number and claim before presenting.
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
Go from a short brief to a structured pitch deck — a PowerPoint in your OneDrive, or a Google Slides deck if you're on Google.
## Parameters
- **source** (required) — the brief, one-pager, or notes to build from.
- **slides** (optional) — target slide count. Defaults to ~10.
## Workflow
1. Read the source material (pasted text, or a Doc / Word / PDF the user names).
2. Structure a standard pitch flow: problem, solution, market, product, business model, traction, team, and the ask. Skip sections the source can't support rather than inventing facts.
3. Write one clear idea per slide — a short title and 2–4 tight bullets.
4. Create the deck in the user's ecosystem: a PowerPoint (.pptx) in OneDrive or Drive, or a native Google Slides deck. Return a clickable link.
5. Post a one-line summary and the link in chat.
## Notes
- A first draft to refine — check every number and claim before presenting.
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
/doc-to-deck
Doc to Deck
Convert a long document into a clean slide deck
---
name: doc-to-deck
description: Convert a long document into a clean slide deck
trigger: /doc-to-deck
user_invocable: true
---
# Doc to Deck
Turn a long document into a presentation — one idea per slide, in your ecosystem.
## Parameters
- **document** (required) — the Google Doc, Word file, or pasted text to convert.
- **slides** (optional) — target length; defaults to what the content needs.
## Workflow
1. Read the document the user names (Google Docs, OneDrive / Word, or pasted text).
2. Map its structure to slides: each major section or heading becomes a slide; condense paragraphs to 2–4 bullets.
3. Add a title slide and a closing summary / next-steps slide.
4. Create the deck — PowerPoint in OneDrive or Drive, or Google Slides — and return a clickable link.
5. Post the link in chat.
## Notes
- Condenses faithfully; it won't add facts the document doesn't contain.
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
Turn a long document into a presentation — one idea per slide, in your ecosystem.
## Parameters
- **document** (required) — the Google Doc, Word file, or pasted text to convert.
- **slides** (optional) — target length; defaults to what the content needs.
## Workflow
1. Read the document the user names (Google Docs, OneDrive / Word, or pasted text).
2. Map its structure to slides: each major section or heading becomes a slide; condense paragraphs to 2–4 bullets.
3. Add a title slide and a closing summary / next-steps slide.
4. Create the deck — PowerPoint in OneDrive or Drive, or Google Slides — and return a clickable link.
5. Post the link in chat.
## Notes
- Condenses faithfully; it won't add facts the document doesn't contain.
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
/board-deck
Board Deck
A monthly board or business-review deck from your numbers and CRM
---
name: board-deck
description: A monthly board or business-review deck from your numbers and CRM
trigger: /board-deck
user_invocable: true
---
# Board Deck
Build a monthly board / business-review deck from your metrics, pipeline, and highlights.
## Parameters
- **month** (optional) — the period to cover; defaults to the current month.
- **source** (optional) — a metrics spreadsheet to pull numbers from.
## Workflow
1. Gather the inputs: a metrics sheet if provided (Sheets or Excel), pipeline and deals from HubSpot if connected, and notable events from the calendar and mail.
2. Assemble the deck: title, KPIs at a glance, revenue and pipeline, wins and risks, and next-period focus.
3. Keep each slide to one message with the key figures called out.
4. Create the deck — PowerPoint in OneDrive or Drive, or Google Slides — and return a clickable link.
5. Post a short summary and the link in chat.
## Notes
- Read-only on your data; it assembles a draft, it changes nothing.
- To build it monthly, say: "run /board-deck on the 1st of each month at 9am".
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
Build a monthly board / business-review deck from your metrics, pipeline, and highlights.
## Parameters
- **month** (optional) — the period to cover; defaults to the current month.
- **source** (optional) — a metrics spreadsheet to pull numbers from.
## Workflow
1. Gather the inputs: a metrics sheet if provided (Sheets or Excel), pipeline and deals from HubSpot if connected, and notable events from the calendar and mail.
2. Assemble the deck: title, KPIs at a glance, revenue and pipeline, wins and risks, and next-period focus.
3. Keep each slide to one message with the key figures called out.
4. Create the deck — PowerPoint in OneDrive or Drive, or Google Slides — and return a clickable link.
5. Post a short summary and the link in chat.
## Notes
- Read-only on your data; it assembles a draft, it changes nothing.
- To build it monthly, say: "run /board-deck on the 1st of each month at 9am".
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
/proposal-deck
Proposal Deck
A client proposal as slides — context, approach, deliverables, pricing
---
name: proposal-deck
description: A client proposal as slides — context, approach, deliverables, pricing
trigger: /proposal-deck
user_invocable: true
---
# Proposal Deck
Turn a client brief into a proposal presentation — the slide companion to a written proposal.
## Parameters
- **client_brief** (required) — who it's for and what they need.
- **source** (optional) — notes, a call summary, or a prior proposal to build from.
## Workflow
1. Gather context: the brief, any related emails with the client, and prior documents if named.
2. Structure the deck: context and understanding, proposed approach, deliverables, timeline, pricing, and next steps.
3. Keep it client-ready — clear, benefit-led, one idea per slide.
4. Create the deck — PowerPoint in OneDrive or Drive, or Google Slides — and return a clickable link.
5. Post the link in chat.
## Notes
- A first draft — review pricing and commitments before sending.
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
Turn a client brief into a proposal presentation — the slide companion to a written proposal.
## Parameters
- **client_brief** (required) — who it's for and what they need.
- **source** (optional) — notes, a call summary, or a prior proposal to build from.
## Workflow
1. Gather context: the brief, any related emails with the client, and prior documents if named.
2. Structure the deck: context and understanding, proposed approach, deliverables, timeline, pricing, and next steps.
3. Keep it client-ready — clear, benefit-led, one idea per slide.
4. Create the deck — PowerPoint in OneDrive or Drive, or Google Slides — and return a clickable link.
5. Post the link in chat.
## Notes
- A first draft — review pricing and commitments before sending.
- Works on both Microsoft (PowerPoint) and Google (Slides) accounts.
Spreadsheets
/expense-log
Expense Log
Log expenses into a running spreadsheet and keep a monthly total
---
name: expense-log
description: Log expenses into a running spreadsheet and keep a monthly total
trigger: /expense-log
user_invocable: true
---
# Expense Log
Capture expenses as you go and keep a tidy running spreadsheet — no app to open, just tell Brain.
## Parameters
- **entry** (optional) — the expense to add, for example "lunch with client, €42, 12 June". If omitted, Brain asks.
## Workflow
1. Find or create an expenses spreadsheet (Excel in OneDrive, or Google Sheets in Google Drive — whichever is connected). Columns: date, description, category, amount, currency.
2. Add the new expense as a row, inferring the category when it's obvious.
3. Update a monthly total (a summary tab or a total row).
4. Reply in chat confirming the row added and the running total for the month.
## Notes
- If a receipt photo is attached, read the amount and merchant from it and log that.
- To get a month-end summary automatically, say: "run /expense-log summary on the last day of each month".
Capture expenses as you go and keep a tidy running spreadsheet — no app to open, just tell Brain.
## Parameters
- **entry** (optional) — the expense to add, for example "lunch with client, €42, 12 June". If omitted, Brain asks.
## Workflow
1. Find or create an expenses spreadsheet (Excel in OneDrive, or Google Sheets in Google Drive — whichever is connected). Columns: date, description, category, amount, currency.
2. Add the new expense as a row, inferring the category when it's obvious.
3. Update a monthly total (a summary tab or a total row).
4. Reply in chat confirming the row added and the running total for the month.
## Notes
- If a receipt photo is attached, read the amount and merchant from it and log that.
- To get a month-end summary automatically, say: "run /expense-log summary on the last day of each month".
/clean-sheet
Spreadsheet Cleanup
Tidy a messy spreadsheet — dedupe, fix formats, sort, and summarise
---
name: spreadsheet-cleanup
description: Tidy a messy spreadsheet — dedupe, fix formats, sort, and summarise
trigger: /clean-sheet
user_invocable: true
---
# Spreadsheet Cleanup
Hand Brain a messy sheet and get back a clean one — consistent formats, no duplicates, sorted, with a quick summary.
## Parameters
- **file** (required) — which spreadsheet to clean (name it, or attach it).
## Workflow
1. Open the spreadsheet from Google Drive or OneDrive (or the attached file).
2. Clean it: trim whitespace, normalise date and number formats, fix obvious typos in categories, and remove exact duplicate rows.
3. Sort by the most useful column and, where helpful, add a summary row or tab (counts, totals).
4. Save a cleaned copy (keep the original untouched) and reply with the file name, what changed, and how many rows were affected.
## Notes
- Never overwrite the original — always save a cleaned copy and report what changed.
- Flag anything ambiguous (for example, two rows that might be the same company) rather than silently merging.
Hand Brain a messy sheet and get back a clean one — consistent formats, no duplicates, sorted, with a quick summary.
## Parameters
- **file** (required) — which spreadsheet to clean (name it, or attach it).
## Workflow
1. Open the spreadsheet from Google Drive or OneDrive (or the attached file).
2. Clean it: trim whitespace, normalise date and number formats, fix obvious typos in categories, and remove exact duplicate rows.
3. Sort by the most useful column and, where helpful, add a summary row or tab (counts, totals).
4. Save a cleaned copy (keep the original untouched) and reply with the file name, what changed, and how many rows were affected.
## Notes
- Never overwrite the original — always save a cleaned copy and report what changed.
- Flag anything ambiguous (for example, two rows that might be the same company) rather than silently merging.
/bank-slip
Bank Slip → Excel
Read a bank statement or slip (photo or PDF) and log the transactions into an Excel sheet
---
name: bank-slip-to-excel
description: Read a bank statement or slip (photo or PDF) and log the transactions into an Excel sheet
trigger: /bank-slip
user_invocable: true
---
# Bank Slip → Excel
Snap or upload a bank statement, deposit slip, or receipt, and get the figures into a tidy spreadsheet — no manual typing.
## Parameters
- **file** (required) — attach the bank slip or statement as a photo or PDF (one or several).
## Workflow
1. Read each attached file — read photos as images, extract the text from PDFs.
2. Pull out the transactions: date, description or payee, amount (with sign — money out vs money in), and the running balance if shown. Capture the account label and statement period when present.
3. Find or create a bank spreadsheet (Excel in OneDrive, or Google Sheets in Google Drive). Append one row per transaction; avoid re-adding a statement that was already logged.
4. Add or update a monthly total: money in, money out, and net.
5. Reply in chat with how many transactions were added, the period covered, and the file name — and flag any line that was unclear so the user can check it.
## Notes
- Numbers read from a photo can be misread — present the result as a draft to verify, and flag any low-confidence amounts.
- Keep the original document untouched; only write to the spreadsheet.
- For privacy, do not store full account numbers — keep just the last few digits or an account label.
- To do it regularly, say: "remind me to log my bank statement on the 5th of each month".
Snap or upload a bank statement, deposit slip, or receipt, and get the figures into a tidy spreadsheet — no manual typing.
## Parameters
- **file** (required) — attach the bank slip or statement as a photo or PDF (one or several).
## Workflow
1. Read each attached file — read photos as images, extract the text from PDFs.
2. Pull out the transactions: date, description or payee, amount (with sign — money out vs money in), and the running balance if shown. Capture the account label and statement period when present.
3. Find or create a bank spreadsheet (Excel in OneDrive, or Google Sheets in Google Drive). Append one row per transaction; avoid re-adding a statement that was already logged.
4. Add or update a monthly total: money in, money out, and net.
5. Reply in chat with how many transactions were added, the period covered, and the file name — and flag any line that was unclear so the user can check it.
## Notes
- Numbers read from a photo can be misread — present the result as a draft to verify, and flag any low-confidence amounts.
- Keep the original document untouched; only write to the spreadsheet.
- For privacy, do not store full account numbers — keep just the last few digits or an account label.
- To do it regularly, say: "remind me to log my bank statement on the 5th of each month".
/invoice-tracker
Invoice Tracker
Scan your inbox for invoices and track paid vs unpaid in a spreadsheet
---
name: invoice-tracker
description: Scan your inbox for invoices and track paid vs unpaid in a spreadsheet
trigger: /invoice-tracker
user_invocable: true
---
# Invoice Tracker
Keep on top of invoices: find them in your mail and track what's paid and what's outstanding.
## Workflow
1. Scan recent mail and its attachments for invoices — supplier, invoice number, amount, date, and due date.
2. Read the amount and due date from each; note any already marked paid.
3. Build or update a spreadsheet (Google Sheets or Excel) with one row per invoice and a **Status** column (unpaid / paid / overdue by due date).
4. Post a summary in chat: total outstanding, anything overdue, and a link to the spreadsheet.
## Notes
- Reads mail and writes a spreadsheet; it never pays or sends anything.
- To run it weekly, say: "run /invoice-tracker every Monday at 9am".
Keep on top of invoices: find them in your mail and track what's paid and what's outstanding.
## Workflow
1. Scan recent mail and its attachments for invoices — supplier, invoice number, amount, date, and due date.
2. Read the amount and due date from each; note any already marked paid.
3. Build or update a spreadsheet (Google Sheets or Excel) with one row per invoice and a **Status** column (unpaid / paid / overdue by due date).
4. Post a summary in chat: total outstanding, anything overdue, and a link to the spreadsheet.
## Notes
- Reads mail and writes a spreadsheet; it never pays or sends anything.
- To run it weekly, say: "run /invoice-tracker every Monday at 9am".
/vat-summary
VAT Summary
Aggregate expenses by category for the quarterly accountant hand-off
---
name: vat-summary
description: Aggregate expenses by category for the quarterly accountant hand-off
trigger: /vat-summary
user_invocable: true
---
# VAT Summary
Pull a period's expenses together, categorised, ready to hand to your accountant.
## Parameters
- **period** (optional) — the quarter or date range; defaults to the last quarter.
## Workflow
1. Gather expense records for the period — an expenses spreadsheet if you keep one, plus invoices and receipts from mail.
2. Categorise each expense (e.g. travel, software, supplies, meals) and capture the amount and, where visible, the VAT / tax portion.
3. Build a spreadsheet (Google Sheets or Excel): one sheet of line items and a summary table of totals per category.
4. Post a summary in chat with the category totals and a link to the spreadsheet.
## Notes
- A preparatory summary for your accountant, not tax advice — have them verify it.
- To run it each quarter, say: "run /vat-summary on the 1st of January, April, July and October".
Pull a period's expenses together, categorised, ready to hand to your accountant.
## Parameters
- **period** (optional) — the quarter or date range; defaults to the last quarter.
## Workflow
1. Gather expense records for the period — an expenses spreadsheet if you keep one, plus invoices and receipts from mail.
2. Categorise each expense (e.g. travel, software, supplies, meals) and capture the amount and, where visible, the VAT / tax portion.
3. Build a spreadsheet (Google Sheets or Excel): one sheet of line items and a summary table of totals per category.
4. Post a summary in chat with the category totals and a link to the spreadsheet.
## Notes
- A preparatory summary for your accountant, not tax advice — have them verify it.
- To run it each quarter, say: "run /vat-summary on the 1st of January, April, July and October".
Meetings & reviews
/meeting-prep
Meeting Prep
A one-page brief before any meeting — who you're meeting, recent context, and talking points
---
name: meeting-prep
description: A one-page brief before any meeting — who you're meeting, recent context, and talking points
trigger: /meeting-prep
user_invocable: true
---
# Meeting Prep
Walk into every meeting prepared: who's attending, your recent history with them, and what to cover.
## Parameters
- **meeting** (optional) — which meeting; defaults to your next calendar event.
## Workflow
1. Find the meeting on the calendar (the next one, or the one the user names) — time, attendees, subject.
2. For each external attendee, gather context: recent emails with them, and, if HubSpot is connected, their company and deal status.
3. Pull any related files from Google Drive or OneDrive the user touched recently on this topic.
4. Produce a one-page brief:
- **Who** — attendees plus one line each
- **Recent context** — last interactions and open items
- **Talking points** — 3–5 suggested points or questions
- **To prepare** — docs to bring, decisions pending
5. Post it in chat.
## Notes
- Read-only; it gathers and summarises, it does not send or change anything.
- To prep automatically before your first meeting each day, say: "run /meeting-prep every weekday at 7am".
Walk into every meeting prepared: who's attending, your recent history with them, and what to cover.
## Parameters
- **meeting** (optional) — which meeting; defaults to your next calendar event.
## Workflow
1. Find the meeting on the calendar (the next one, or the one the user names) — time, attendees, subject.
2. For each external attendee, gather context: recent emails with them, and, if HubSpot is connected, their company and deal status.
3. Pull any related files from Google Drive or OneDrive the user touched recently on this topic.
4. Produce a one-page brief:
- **Who** — attendees plus one line each
- **Recent context** — last interactions and open items
- **Talking points** — 3–5 suggested points or questions
- **To prepare** — docs to bring, decisions pending
5. Post it in chat.
## Notes
- Read-only; it gathers and summarises, it does not send or change anything.
- To prep automatically before your first meeting each day, say: "run /meeting-prep every weekday at 7am".
/monthly-summary
Monthly Summary
A monthly review of what happened — meetings, deliverables, and highlights
---
name: monthly-summary
description: A monthly review of what happened — meetings, deliverables, and highlights
trigger: /monthly-summary
user_invocable: true
---
# Monthly Summary
Close the month with a clear recap: where your time went, what got delivered, and what's carrying into next month.
## Workflow
1. Read last month's calendar (meetings by type and volume) and recent mail for shipped work and open threads.
2. If a task tool is connected, pull what was completed versus still open.
3. Produce a summary: **highlights**, **delivered**, **in progress**, **carry-over for next month**, plus a few numbers (meeting count, hours in meetings if available).
4. Offer to save it as a document (Word or Google Docs) and post the summary in chat.
## Notes
- Read-only review; it doesn't change anything.
- To get it on the first of each month, say: "run /monthly-summary on the 1st of each month at 8am".
Close the month with a clear recap: where your time went, what got delivered, and what's carrying into next month.
## Workflow
1. Read last month's calendar (meetings by type and volume) and recent mail for shipped work and open threads.
2. If a task tool is connected, pull what was completed versus still open.
3. Produce a summary: **highlights**, **delivered**, **in progress**, **carry-over for next month**, plus a few numbers (meeting count, hours in meetings if available).
4. Offer to save it as a document (Word or Google Docs) and post the summary in chat.
## Notes
- Read-only review; it doesn't change anything.
- To get it on the first of each month, say: "run /monthly-summary on the 1st of each month at 8am".
/week-planner
Week Planner
Review the week ahead — conflicts, gaps, and protected focus time
---
name: week-planner
description: Review the week ahead — conflicts, gaps, and protected focus time
trigger: /week-planner
user_invocable: true
---
# Week Planner
Look at the week ahead and turn a full calendar into a workable plan.
## Workflow
1. Read the upcoming week's events from the connected calendar (Google or Outlook).
2. Flag issues: back-to-back stretches, double-bookings, days with no free block, and meetings without a clear purpose.
3. Suggest a plan: propose 1–2 protected focus blocks on the lighter days and note anything worth declining or shortening.
4. Post a day-by-day overview in chat with the suggestions.
## Notes
- Read-only; it proposes, it doesn't move or create events unless you ask.
- To get it every Sunday evening, say: "run /week-planner every Sunday at 6pm".
Look at the week ahead and turn a full calendar into a workable plan.
## Workflow
1. Read the upcoming week's events from the connected calendar (Google or Outlook).
2. Flag issues: back-to-back stretches, double-bookings, days with no free block, and meetings without a clear purpose.
3. Suggest a plan: propose 1–2 protected focus blocks on the lighter days and note anything worth declining or shortening.
4. Post a day-by-day overview in chat with the suggestions.
## Notes
- Read-only; it proposes, it doesn't move or create events unless you ask.
- To get it every Sunday evening, say: "run /week-planner every Sunday at 6pm".
/time-audit
Time Audit
Where last week went — meeting load vs focus time, by category
---
name: time-audit
description: Where last week went — meeting load vs focus time, by category
trigger: /time-audit
user_invocable: true
---
# Time Audit
See where your time actually went last week, so you can adjust the next one.
## Parameters
- **period** (optional) — the week to analyse; defaults to last week.
## Workflow
1. Read the period's calendar events from the connected account.
2. Categorise the time: internal meetings, external / client meetings, 1:1s, focus / no-meeting blocks, and recurring vs one-off.
3. Total the hours per category and compute meeting load vs unbroken focus time.
4. Post a short breakdown in chat with 2–3 observations (e.g. "62% in meetings, no focus block on Tue/Thu").
## Notes
- Read-only summary based on calendar data.
- To get it every Friday, say: "run /time-audit every Friday at 5pm".
See where your time actually went last week, so you can adjust the next one.
## Parameters
- **period** (optional) — the week to analyse; defaults to last week.
## Workflow
1. Read the period's calendar events from the connected account.
2. Categorise the time: internal meetings, external / client meetings, 1:1s, focus / no-meeting blocks, and recurring vs one-off.
3. Total the hours per category and compute meeting load vs unbroken focus time.
4. Post a short breakdown in chat with 2–3 observations (e.g. "62% in meetings, no focus block on Tue/Thu").
## Notes
- Read-only summary based on calendar data.
- To get it every Friday, say: "run /time-audit every Friday at 5pm".
Research
/competitor-briefing
Competitor & Topic Briefing
A short daily web briefing on the competitors and topics you care about
---
name: competitor-briefing
description: A short daily web briefing on the competitors and topics you care about
trigger: /competitor-briefing
user_invocable: true
---
# Competitor & Topic Briefing
A quick daily read on what moved in your market — competitor news, product launches, and the topics you track.
## Parameters
- **competitors / topics** (required the first time) — the names and themes to watch. Brain remembers them for next time.
## Workflow
1. If no watch-list is set yet, ask the user for the competitors and topics to follow, and remember them.
2. Search the web for recent, relevant news on each item (last 24–48 hours).
3. Cross-check across sources and drop anything stale or duplicated.
4. Produce a briefing: per competitor/topic, 1–3 bullet points on what happened and why it matters, naming the source.
5. Post it in chat.
## Notes
- Name the source for each item so the user can judge reliability; flag anything uncertain rather than stating it as fact.
- To get it every weekday morning, say: "run /competitor-briefing every weekday at 7am".
A quick daily read on what moved in your market — competitor news, product launches, and the topics you track.
## Parameters
- **competitors / topics** (required the first time) — the names and themes to watch. Brain remembers them for next time.
## Workflow
1. If no watch-list is set yet, ask the user for the competitors and topics to follow, and remember them.
2. Search the web for recent, relevant news on each item (last 24–48 hours).
3. Cross-check across sources and drop anything stale or duplicated.
4. Produce a briefing: per competitor/topic, 1–3 bullet points on what happened and why it matters, naming the source.
5. Post it in chat.
## Notes
- Name the source for each item so the user can judge reliability; flag anything uncertain rather than stating it as fact.
- To get it every weekday morning, say: "run /competitor-briefing every weekday at 7am".
/company-shortlist
Company Shortlist
Research companies matching your criteria and drop a sorted spreadsheet in your Drive
---
name: company-shortlist
description: Research companies matching your criteria and drop a sorted spreadsheet in your Drive
trigger: /company-shortlist
user_invocable: true
---
# Company Shortlist
Turn a research question into a tidy, sortable list — companies that match your criteria, in a spreadsheet ready to use.
## Parameters
- **criteria** (required) — sector, geography, size or revenue, or any filter (for example: "medical-device makers in France above €50M revenue").
## Workflow
1. Confirm the criteria with the user if anything is ambiguous.
2. Search the web and compile candidate companies, cross-checking figures across sources.
3. Build a spreadsheet — Excel in OneDrive, or Google Sheets in Drive, whichever the user has connected — with columns: company, sector, revenue, location, source, notes.
4. Sort it sensibly (for example by revenue) and save it to the user's Drive.
5. Reply in chat with the file name and link, noting that it's a first cut to verify before sending.
## Notes
- Figures from the web can be wrong — present this as a first draft to check, not a final answer.
- Flag any company where the data was thin or uncertain.
- This is a one-off; to repeat it on a schedule (for example a quarterly market scan), say so and Brain will set it up.
Turn a research question into a tidy, sortable list — companies that match your criteria, in a spreadsheet ready to use.
## Parameters
- **criteria** (required) — sector, geography, size or revenue, or any filter (for example: "medical-device makers in France above €50M revenue").
## Workflow
1. Confirm the criteria with the user if anything is ambiguous.
2. Search the web and compile candidate companies, cross-checking figures across sources.
3. Build a spreadsheet — Excel in OneDrive, or Google Sheets in Drive, whichever the user has connected — with columns: company, sector, revenue, location, source, notes.
4. Sort it sensibly (for example by revenue) and save it to the user's Drive.
5. Reply in chat with the file name and link, noting that it's a first cut to verify before sending.
## Notes
- Figures from the web can be wrong — present this as a first draft to check, not a final answer.
- Flag any company where the data was thin or uncertain.
- This is a one-off; to repeat it on a schedule (for example a quarterly market scan), say so and Brain will set it up.
CRM
/deal-triage
HubSpot Deal Triage
Weekly HubSpot pipeline review — stale deals, deals needing action, and next steps
---
name: deal-triage
description: Weekly HubSpot pipeline review — stale deals, deals needing action, and next steps
trigger: /deal-triage
user_invocable: true
---
# HubSpot Deal Triage
Keep the pipeline honest: surface deals that have gone quiet, deals close to a decision, and the next action for each.
## Workflow
1. Read the open deals from HubSpot (stage, amount, close date, last activity).
2. Flag each one as:
- **Stale** — no activity in 14+ days
- **Closing soon** — close date within 14 days
- **Missing next step** — no task or next action set
3. For each flagged deal, suggest a concrete next step — a follow-up email draft, a call reminder, or a stage update.
4. Post a short triage report in chat, grouped by the three buckets, with the suggested action per deal.
## Notes
- Suggest changes only; update HubSpot or send emails after the user approves.
- The "stale" threshold (14 days) and "closing soon" window (14 days) can be adjusted — just say so.
- To run it weekly, say: "run /deal-triage every Monday at 9am".
Keep the pipeline honest: surface deals that have gone quiet, deals close to a decision, and the next action for each.
## Workflow
1. Read the open deals from HubSpot (stage, amount, close date, last activity).
2. Flag each one as:
- **Stale** — no activity in 14+ days
- **Closing soon** — close date within 14 days
- **Missing next step** — no task or next action set
3. For each flagged deal, suggest a concrete next step — a follow-up email draft, a call reminder, or a stage update.
4. Post a short triage report in chat, grouped by the three buckets, with the suggested action per deal.
## Notes
- Suggest changes only; update HubSpot or send emails after the user approves.
- The "stale" threshold (14 days) and "closing soon" window (14 days) can be adjusted — just say so.
- To run it weekly, say: "run /deal-triage every Monday at 9am".
Utilities
/translate
Translate
Translate a document or email while keeping its formatting and tone
---
name: translate
description: Translate a document or email while keeping its formatting and tone
trigger: /translate
user_invocable: true
---
# Translate
Translate an email, document, or pasted text into another language — keeping the formatting, tone, and intent.
## Parameters
- **text / file** (required) — what to translate (paste it, or name a file in your Drive).
- **target language** (required) — the language to translate into.
## Workflow
1. Read the source text or file.
2. Translate it accurately into the target language, preserving structure (headings, lists, paragraphs) and matching the register (formal vs casual) of the original.
3. For documents, save the translation as a new file (keep the original); for emails, prepare a draft.
4. Reply with the translation (or the file name), and flag any phrase that didn't translate cleanly.
## Notes
- Keep names, figures, and links exactly as in the source.
- Email translations are drafts — never sent automatically.
Translate an email, document, or pasted text into another language — keeping the formatting, tone, and intent.
## Parameters
- **text / file** (required) — what to translate (paste it, or name a file in your Drive).
- **target language** (required) — the language to translate into.
## Workflow
1. Read the source text or file.
2. Translate it accurately into the target language, preserving structure (headings, lists, paragraphs) and matching the register (formal vs casual) of the original.
3. For documents, save the translation as a new file (keep the original); for emails, prepare a draft.
4. Reply with the translation (or the file name), and flag any phrase that didn't translate cleanly.
## Notes
- Keep names, figures, and links exactly as in the source.
- Email translations are drafts — never sent automatically.
On a team? Browse your organisation's skills
Colleagues on your work-email domain can share skills with each other. Sign in with Google or Microsoft to see the ones your organisation has shared — then copy any into your chat.
