All Prompts

Help me identify repetitive tasks in my work or business that may be suitable for automation. I will describe the work my team or I repeat. For each task, assess: - how often it happens; - how consistent the steps are; - whether inputs are structured or predictable; - whether rules are clear; - amount of human judgement required; - consequences of an error; - sensitivity of the data involved; - whether a human approval point is important. Classify each task as: - Good candidate to explore - Possible candidate with human review - Poor candidate for automation - Need more information Explain the reasoning in plain English. Then suggest what I should measure or document before deciding whether automation is worthwhile, such as time spent, volume, error rate or common exceptions. Important boundary: - Do not design the automation. - Do not give Make, Zapier, n8n, API or agent implementation steps. - Do not recommend automating high-stakes judgement merely because it repeats. - Flag privacy/security considerations where sensitive information is involved. Repeated tasks/processes: [DESCRIBE THEM]

Turn my project notes into a clear client update. Context: - Project: [PROJECT] - Client/audience: [AUDIENCE] - Update period: [OPTIONAL] - Tone: [OPTIONAL] Use only the facts in my notes. Structure the update around: 1. Progress since the last update 2. Completed items or decisions 3. Current work 4. Blockers or risks the client genuinely needs to know about 5. Information/approval needed from the client 6. Next steps and dates, only where supplied Keep internal chatter, uncertainty and implementation detail out unless it affects the client. Do not make progress sound stronger than my notes support. Preserve important caveats and dependencies. If an action needs an owner or date that I have not provided, mark it for clarification rather than inventing one. My notes: [PASTE NOTES]

Draft a polite overdue invoice reminder. Details: - Client/customer name: [NAME] - Invoice number: [INVOICE NUMBER] - Invoice amount: [AMOUNT] - Original due date: [DATE] - How overdue it is: [OPTIONAL] - Previous reminder/contact: [OPTIONAL] - Payment method/details to mention: [OPTIONAL] - Tone: [FRIENDLY / NEUTRAL / FIRMER] Write a concise email that: 1. States which invoice is outstanding. 2. Mentions the due date factually. 3. Asks for payment or a clear update. 4. Leaves room for the possibility that payment has already been sent or there is a genuine issue. 5. Includes the next practical step I supplied. Do not invent late fees, contractual rights, legal threats or escalation steps. If I want a firmer reminder, make the wording firmer without adding consequences I have not confirmed. Output: - Subject line - Email body

Turn this client feedback into clear revision actions. I will provide the feedback and, if useful, the work/brief it refers to. Separate the feedback into: - Confirmed changes requested - Preferences/suggestions rather than firm changes - Questions from the client - Positive feedback worth preserving - Conflicting or ambiguous comments - Requests that appear outside the original brief, only if I also provide the brief For each confirmed change create an action with: - what to change; - where it applies; - any constraint the client stated; - clarification needed, if any. Then order the actions logically so dependent changes happen in the right sequence. Finish with a short list of clarification questions for anything ambiguous or contradictory. Do not invent a solution the client did not request. Do not make commercial decisions about scope or fees for me. Client feedback: [PASTE] Original brief/work: [OPTIONAL: PASTE OR ATTACH]

Find the missing information in this client brief before I start the work. Brief: [PASTE OR ATTACH] My type of work: [DESIGN / CONTENT / DEVELOPMENT / CONSULTING / OTHER] Review the brief for clarity on: - objective/outcome; - audience/users; - deliverables; - scope boundaries; - source material/assets; - brand or technical constraints; - deadline/milestones; - decision-maker/approvals; - success criteria; - dependencies on the client or third parties. Create three groups: 1. Clear enough to proceed 2. Useful to clarify 3. Blocking information — work risks going in the wrong direction without it For every gap, draft one concise question I can ask the client. Do not turn this into a full project scope, proposal or consultancy plan. The goal is to identify what is missing from the supplied brief.

Draft questions to clarify this supplier quote. My project/need: [CONTEXT] Quote: [PASTE OR ATTACH] What I am already unsure about: [OPTIONAL] Identify questions only where the quote is ambiguous, incomplete or dependent on an assumption that matters. Group them under headings such as: - Scope and deliverables - Price and extras - Timing - Responsibilities/dependencies - Support/warranty - Changes/cancellation For each question, make it: - neutral; - specific; - answerable; - free of unnecessary negotiation language. Then draft a short email containing the highest-priority questions in a sensible order. Do not add generic procurement questions just to make the list longer. Do not provide legal advice about the quote.

Find extra costs, exclusions or assumptions in these supplier quotes. Focus on details that are stated, implied by the quote's own assumptions, or missing and worth clarifying. Do not invent costs simply because they might exist. Review for: - excluded work; - optional extras; - minimum quantities; - travel, delivery or installation; - taxes/fees if mentioned; - setup or recurring charges; - customer-supplied materials or work; - assumptions about access, data, timing or approvals; - price changes after a period or threshold; - cancellation/change terms stated in the quote. Create a table with: - Quote/supplier - Item or assumption - What the document says - Possible cost/scope impact - Clarification needed: Yes / No Then identify the 5 questions most worth asking before I compare the final cost. Do not invent unstated fees. If a typical cost is not mentioned, phrase it as a clarification question, not a claim. Quotes: [PASTE OR ATTACH]

Compare these supplier quotes side by side. My goal or project: [WHAT I AM BUYING / PROJECT CONTEXT] What matters most to me: [PRICE / QUALITY / SPEED / SCOPE / SUPPORT / OTHER] Use only the quotes and context I provide. Build a comparison table covering where available: - total quoted price; - what is included; - what is excluded; - quantities or assumptions; - delivery/timing; - payment terms; - warranties/support; - optional extras; - dependencies or customer responsibilities; - validity period. For each comparison point, use "Not stated" rather than assuming missing terms. Then summarise: 1. Clear differences. 2. Items that are not directly comparable because scope differs. 3. Important information missing from one or more quotes. 4. Questions I should resolve before comparing headline prices. Do not tell me which supplier to choose unless I explicitly provide decision criteria. Do not provide legal or financial advice about contract terms. Quotes: [PASTE OR ATTACH QUOTES]

Turn this successful prompt into a reusable template. Original prompt: [PASTE PROMPT] What I used it for: [CONTEXT] What worked well about the result: [WHAT I LIKED] Identify: - instructions that should stay fixed; - details that should become placeholders; - accidental one-off context that should be removed; - unnecessary wording that can be shortened; - important constraints worth keeping. Then create a reusable version using clear square-bracket placeholders such as [AUDIENCE], [SOURCE MATERIAL] or [DESIRED OUTCOME]. Rules: - Use as few placeholders as practical. - Keep the template understandable to someone using it months later. - Do not preserve fake personas or filler unless they genuinely affected the task. - Add a brief "How to use this" note explaining what the user should replace or attach. Finish with a one-line description of the kind of task the template is good for.

Help me remove sensitive information before I share this text with an AI tool. Text: [PASTE TEXT] My task for the AI will be: [WHAT I WANT THE AI TO DO] Review the text for information that may be unnecessary for that task, including where relevant: - full names; - personal email addresses or phone numbers; - home addresses; - account, customer, case, employee or reference numbers; - passwords, API keys, tokens or security codes; - private financial details; - confidential business information; - information about other identifiable people; - exact dates or locations that are not needed. Output: 1. Sensitive details found — describe the type, not the secret itself where possible. 2. Whether each detail appears necessary for my stated task. 3. A sanitised version of the text using clear placeholders such as [CUSTOMER NAME], [ACCOUNT NUMBER] or [DATE]. 4. Anything I should avoid sharing entirely rather than merely redact. Do not claim that redaction guarantees privacy. Keep enough context for the task to remain usable without retaining unnecessary identifying detail.