Practical prompts you can copy into any AI assistant. Replace the {curly} placeholders with your own details, and never paste personal or confidential data into a tool your organisation hasn't approved.
Marketing
LinkedIn Post Rewriter
Turn a rough idea into a scroll-stopping LinkedIn post with a hook, story, and CTA.
You are a senior B2B LinkedIn ghostwriter. Rewrite the draft below into a post that opens with a 1-line hook, uses short paragraphs (1-2 sentences), includes a specific concrete detail, and ends with a question CTA. Keep it under 1200 characters. No hashtags in the body — put 3 relevant hashtags at the end.\n\nDRAFT:\n{{draft}}
Generate a 3-line personalized cold email using a prospect's public info.
You are an outbound SDR at a Canadian tech company. Given the prospect data below, write a 3-sentence cold email:\n1) A specific compliment tied to something they actually did.\n2) A one-sentence hypothesis about a pain we can solve.\n3) A soft ask for a 15-min call, with 2 concrete time options.\n\nNo jargon. No "I hope this finds you well." Sign off with just my first name.\n\nPROSPECT: {{prospect_info}}\nMY OFFER: {{offer}}
Productivity
Meeting Notes → Action Items
Extract owner-assigned action items and decisions from any meeting transcript.
You are a chief of staff. From the transcript below, output:\n\nDECISIONS: bullet list of decisions made.\nACTION ITEMS: table with columns Owner | Action | Due Date (assume 1 week if not stated).\nOPEN QUESTIONS: bullet list.\n\nIgnore small talk. Be concise. If an owner is unclear, write "?".\n\nTRANSCRIPT:\n{{transcript}}
HR
Job Description Rewriter
Rewrite a boring JD into one that attracts strong candidates.
You are a technical recruiter at a top Canadian tech company. Rewrite the job description below so it:\n- Opens with what the person will actually build in their first 90 days.\n- Lists 5 concrete responsibilities (no "wear many hats").\n- Lists 5 must-have skills (no "5+ years of X" unless truly needed).\n- Removes gendered/exclusionary language.\n- Ends with pay range in CAD, remote policy, and one sentence on team culture.\n\nJD:\n{{jd}}
Engineering
SQL Explainer
Explain any SQL query in plain English step-by-step.
You are a senior data engineer. Explain the SQL query below to a business analyst who understands spreadsheets but not SQL. Structure:\n1) One-sentence summary of what the query returns.\n2) Step-by-step walkthrough (numbered, plain English).\n3) Any performance concerns or missing indexes to flag.\n\nSQL:\n{{sql}}
Draft an empathetic, on-brand support reply from a customer ticket.
You are a customer support agent at a Canadian SaaS company. Write a reply to the customer message below.\nRules:\n- Acknowledge the specific problem in the first sentence.\n- Do not apologize more than once.\n- Give the exact next step (numbered if multiple).\n- Set a clear expectation on timing.\n- Warm sign-off with first name only.\n\nCUSTOMER MESSAGE:\n{{message}}\n\nCONTEXT ABOUT OUR PRODUCT:\n{{context}}
Leadership
Weekly Executive Brief
Turn raw team updates into a one-page executive brief.
Generate role-specific interview questions with rubrics.
Included with enrolled programs.
Finance
Month-End Variance Explainer
Turn a budget-vs-actual table into a plain-English variance commentary for management.
You are a senior financial analyst. Below is a budget-vs-actual table for {period}. For each line with a variance above {threshold}%, explain the likely drivers, state what you would verify before reporting, and flag anything that needs an accountant's judgement. Do not invent figures that are not in the table. Output: a short summary paragraph, then a bullet per material variance.
TABLE:
{paste table}
Extract structured fields from an invoice and list anything that looks inconsistent.
Extract these fields from the invoice text below as JSON: vendor_name, invoice_number, invoice_date, due_date, currency, subtotal, tax_amounts (by tax type, e.g. GST/HST/QST), total. If a field is missing write null. After the JSON, list any inconsistencies (e.g. subtotal + tax not equal to total). Never guess a number.
INVOICE:
{paste invoice text}
Review a draft internal AI use policy against common governance topics.
Act as an AI governance reviewer. Review the policy below and report which of these topics it covers, partially covers, or omits: approved tools, data classification and what may not be entered, personal information handling (PIPEDA / provincial law), human review of outputs, accountability owner, incident reporting, vendor review, record keeping, training. For each gap, suggest one sentence of policy wording. Note that this is not legal advice.
POLICY:
{paste policy}
Generate a vendor questionnaire for an AI tool before procurement.
You are helping a Canadian organisation evaluate the AI vendor "{vendor}" for the use case "{use case}". Write 15 due-diligence questions grouped under: data residency and retention, training on customer data, security controls and certifications, model accuracy and evaluation, human oversight, incident notification, contract exit. For each question, add one line on what a good answer looks like.
Classify a suspicious email and explain the indicators found.
You are a security analyst. Analyse the email below (headers and body). Report: verdict (likely phishing / suspicious / likely legitimate), the specific indicators you found (sender domain mismatch, urgency, link targets, attachments), and recommended next steps for the employee and for IT. Do not click or fetch any links; reason only from the text.
EMAIL:
{paste email}
Draft test inputs to check an LLM app against prompt injection.
I am testing my own LLM application, which does: {describe app and its tools}. Write 12 test inputs that attempt prompt injection or data exfiltration (direct instructions, instructions hidden in retrieved documents, role-play, encoding tricks). For each, state the expected safe behaviour so I can grade the result. Only for testing systems I own.
Rewrite administrative patient notices in plain language (no clinical advice).
Rewrite the administrative notice below for patients at a grade 6 reading level. Keep every date, time, location and instruction exactly as written. Do not add medical advice. Offer a version in English and in French. Remove any personal health information before pasting.
NOTICE:
{paste notice}
Check whether an LLM answer is supported by the retrieved passages.
Given the QUESTION, the retrieved PASSAGES (numbered), and the ANSWER, check each claim in the answer. For every claim output: the claim, supported / partially supported / unsupported, and the passage number(s) that support it. Finish with a grounding score = supported claims / total claims.
QUESTION: {q}
PASSAGES: {passages}
ANSWER: {answer}
Score a list of manual tasks for automation potential.
Below is a list of recurring manual tasks with rough weekly hours. For each, rate automation suitability (high/medium/low) based on: rule-based vs judgement-heavy, input format consistency, error cost, and volume. Suggest the simplest tool type (spreadsheet formula, workflow tool, script, LLM step) and one risk to manage. Sort by estimated hours saved.
TASKS:
{paste list}
Generate ad copy variants from a brief while respecting claim rules.
From the campaign brief below, write 5 headline + description variants for search ads (headline max 30 characters, description max 90). Use only claims stated in the brief; do not invent statistics, prices or guarantees. Mark which variant targets which audience segment.
BRIEF:
{paste brief}