Our suggested starting prompt — not the author's original · untested
You'll need: The original setup uses written Claude Code rules and skills, previous posts, topic sources, and a WhatsApp approval connection. The exact instructions and connection method are not supplied.
Read my last ten LinkedIn posts in [folder] and my notes for this week. Identify the recurring features of my writing, then draft five posts with one clear point each. Use only facts supported by my notes or sources, and flag any gaps. Save the drafts in [folder] for my review. Do not publish them.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code on a paid Claude plan, plain-English rules and skill files, Google Ads Keyword Planner access and publishing access to your website. The review rubric, the website platform and how the keyword tool is connected are not disclosed.
When I publish a new post, turn it into a blog article of [length] for our website. Check what people search for on this topic and read the top results first, then write an original article that expands my point with examples. Score your draft against [checklist] and save it as a draft in [CMS/folder] for me to review. Don't publish.
You'll need: Claude Code on a paid Claude plan, plain-English rules and skill files, read access to your CRM, email and WhatsApp, and a schedule. Which CRM, how it is connected and how priority is decided are not disclosed.
| Section | Example line |
| --- | --- |
| Job | Every Monday at 8:00, write a one-page pipeline summary for the founder. |
| Inputs | Open deals in the CRM, read only. Last week's call notes in /notes. |
| Voice | Short sentences, first person plural, numbers before adjectives. |
| Never | Send email, change a deal stage or delete a file. |
| Done means | Every open deal is listed with its next step, owner and date. |
| Mistakes log | YYYY-MM-DD: listed a closed deal as open. Check the stage field first. |
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code connected to AI Ark, Clay, an email-finding tool (named only as "LM") and Bison. The prompts, how the tools were connected and any review steps are not disclosed.
Help me set up a cold email campaign for [offer] aimed at [ideal customer]. Pull a list of [N] matching companies from [lead tool], check each one against my criteria [list] and drop the ones that don't fit, find a contact email for the right person, and draft a 3-step sequence. Load everything into [sending tool] as a paused draft campaign. Don't start sending; show me 5 sample emails first.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot; Amazon seller API access connected to the bot; Sellerboard (or similar) with cost-of-goods data and a bot user login; several months of sales/refund history. Exact thresholds, table columns, API setup details, and model are not disclosed.
Using my connected Amazon seller data and Sellerboard, look at the last 6 months for every ASIN. Build a table with units sold, revenue, refund count and refund rate, Amazon fees, cost of goods (from Sellerboard) and net profit. Flag ASINs with high sales but a high refund rate and little or no profit. Then check which flagged ASINs are back in stock or due for a reorder and, for each one, say whether it looks worth replenishing and why, showing the numbers. If cost data is missing for an ASIN, write 'unknown' instead of guessing. Don't place, change or cancel any orders, listings or shipments; this is a recommendation for me to review.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your estimate schedule and pricing; estimating and proposal templates; a voice or text summary of each site visit. Which apps are connected, pricing math, sheet formats, and model are not disclosed.
I just finished a site visit. The customer wants [number] projects quoted separately: [for each project: scope, measurements, materials, special conditions]. Using my estimating sheet and proposal template, draft a separate estimate and proposal for each project. Use my standard pricing from the sheet, and list any line item where you had to assume a quantity, price or scope, marked 'check'. Keep each proposal in my usual format and tone. Don't send anything to the customer; save the drafts for me to review.
You'll need: Grok Bot connected to the mailbox where customers write in (author used Gmail), with permission to create drafts; a shipped feature and the words customers used to ask for it. How Gmail was connected and whether, how or when the drafts were sent are not disclosed.
Go over ALL my HabitKit support emails and check for people who wished for a "Quit habits / Inverse habits" feature (where habits are checked on by default) in HabitKit. Draft a message for them that tell them that it finally landed in the app, apologize that it was a long time coming. Say that I would be super happy if they would check it out. Only drafts in my Gmail!
Have Claude Cowork read each applicant's resume, draft personalized outreach and replies for the author to edit and send, set up interview booking and a candidate tracker, and prepare offer letters, while the author does the interviews and makes the hiring decisions with the team.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; access to the inbox where applications arrive (drafts only); a scheduling link such as Calendly and a calendar; a candidate tracking document; an offer-letter template and agreement; an e-signature tool such as DocuSign used by the owner; clear role criteria; the owner's review of every email before sending
Help me run a hiring round for [roles]. Here are the role descriptions and what success looks like for each: [criteria]. Applications arrive by email at [inbox/label]. For each applicant, read their resume and write a short summary of relevant experience, strengths and open questions against only my stated criteria, noting if they might fit another open role. Don't rank or reject anyone. Draft a personalized reply to each applicant inviting them to book an interview at [scheduling link], and save it as a draft for me to review; do not send anything. Keep a tracking document with each candidate's status (invite drafted, booked, interviewed, decision) and tell me who hasn't booked. After interviews I'll add my notes; update the summaries. When I tell you who gets an offer and the terms, fill in [offer letter template] for each and save PDFs for me to review and sign. Draft a personal note for each candidate not selected, as a draft only. Don't delete emails, accept or cancel meetings, or contact anyone yourself.
Have Claude Code or Codex work through a bookkeeping backlog: read receipts and invoices, propose accounts and VAT, match bank rows, and stage draft entries that wait for your approval before anything is posted.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code or Codex with your own Anthropic or OpenAI subscription; a bookkeeping platform the agent can reach through a CLI or MCP server with a stage-then-approve queue (he used Igdrasil); your receipts, invoices and bank feed in that platform; a practice company for testing; your rules for voucher series, recurring accounts and what should wait; your own approval of every posting and anything sent to the tax authority
You're helping me with the books for my company [name] in [bookkeeping tool], which you can reach through its CLI/MCP. Work in drafts only. First, list what is unmatched in the bank right now and group the rows. For each group, read the linked receipts or invoices and propose the account, VAT code and business purpose, and flag anything unclear, new suppliers, mixed VAT or unpaid supplier invoices for me instead of guessing. Use voucher series [series] and these rules: [account rules, what should wait]. Create draft entries and stage them for my approval, then check the draft set for duplicates and show me a list of what you staged. Do not post, approve, correct or delete anything, file or send anything to the tax authority, export to other systems, create test entries, or change any code. After I approve a batch and it's posted, read the ledger back and give me a reconciliation, not a summary.
Have Claude Code run a skill that drafts your monthly client invoices from your time reports and calendar, creates them in Xero, emails them from Gmail and checks last month's payments, pausing for your check before invoices are created and before they are marked paid.
You'll need: Claude Code; a Claude skill describing your monthly invoicing steps; access from Claude Code to your time tracker (Toggl), accounting software (Xero), calendar (Google Calendar), email (Gmail) and a notes app for the task list (Obsidian); your client rates and invoicing rules; your own review at the skill's checkpoints (after the time reports, before invoices are created in Xero, and before invoices are marked paid); the post states no check right before invoices are emailed, so our suggested prompt adds one
Hey Claude, I'm a freelancer and I have to send invoices every month and also verify that my past month's invoices were paid. Could you help me make a skill to do this?
Have Claude run a client-onboarding skill that drafts the client's contract, creates their shared Slack channel, adds them to your client database, and prepares samples, website mockups and a podcast feed for your review, while you send the invites, grant access and write the client messages yourself.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude with skills (or saved instructions) describing your onboarding process; your internal docs, past contracts and the client's correspondence; access to your documents (for example Google Drive and Docs) and, if you let it do setup steps, to your team chat (the author used Slack via Claude's browser use) and client database; your own review of the contract, every account, channel or access change, and every client message. Building the skills was a one-off investment of about a day of the author's time, by his estimate.
Help me onboard a new client for my [type of service] business. Work in stages and stop for my approval at the end of each one.
Stage 0 (first time only): Read my internal docs and past client notes in [folder]. Write a short overview of what my business does and how it works, then draft a step-by-step client onboarding checklist. I'll correct it. Once I approve it, save it as reusable instructions I can run for future clients.
Stage 1, contract: Using the client emails and call notes I've attached and my past contracts in [folder], draft a service contract for [client] as a document. Look up their public details (legal name, registered address, registration number) and list where you found each one. Highlight anything that differs from my usual contract or that you're unsure about. Don't send it or upload it to a signing service. I'll review it and send it myself.
Stage 2, setup: List every channel, record and account this client needs (for example a shared [Slack] channel that follows my naming pattern, or an entry in my client database), and wait for my OK before you create each one. Don't invite the client, grant access, change permissions, or enter any password or payment details. Give me the invite link or the exact page to open, and I'll do those steps.
Stage 3, tailoring and samples: Review [the client's website or materials], list the special cases my service needs to handle for them, and propose a rule for each. After I approve the rules, prepare [sample deliverables] for me to check, and flag anything you're unsure about.
Stage 4, mockups and delivery setup: Make mockups of [how my deliverable would look on their website], using their public branding, and draft [the feed, page or other delivery setup] privately. Don't publish anything until I approve it.
Stage 5, client update: Don't write or send messages to the client. Give me a bullet list of points to cover in my update, then check my draft for clarity and for anything I've missed.
Finish with a checklist of what's done, what's waiting for my approval, and what I need to do myself.
Have Claude Cowork use your calendar to work out a month's mileage for two work trucks, match it against your gas receipts and flag what does not line up for your review.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork (the author's setup) with access to your calendar and to the email address or folder where gas receipts arrive; a consistent calendar convention (client site, and which vehicle, on every entry); your own rules for what to flag; your own review of every flagged mismatch before the figures are used.
Help me prepare my mileage and fuel log for [month]. Use my calendar for that month: each client visit should show the client site and, in [the title or notes], which vehicle I used ([Truck A or Truck B]). Look at the gas receipts in [the mailbox or folder where they arrive]. For each visit, work out the miles driven from [my starting address] and show how you worked out the distance. Then match each gas receipt to a vehicle and a date. Give me a table with date, client site, vehicle, miles and matched receipt(s). Do not guess. In a separate list, show every entry with no vehicle or an unclear location, every receipt that does not match a trip, and any gap or overlap, and say what is missing. Do not change my calendar, email or files; give me the table and the list to review.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to wherever your receipts and expense records live (the post does not say where); a place to keep the expense list (the post does not say whether it is a spreadsheet or an app); your own review of the list and categories before you rely on it.
Help me keep my expenses and receipts in order for [month]. Look in [the places my receipts and statements arrive, for example a receipts email address, a folder, or a bank export I upload]. For each expense, record the date, vendor, amount, category (use these categories: [list]) and which receipt supports it, in a spreadsheet called [name]. Then give me a separate list of any expense with no receipt, any receipt with no matching expense, possible duplicates, and anything you categorised with low confidence. Do not pay, cancel or change anything, do not contact vendors, and do not send anything to my accountant; give me the sheet and the list for my review.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with enough access to, or notes about, the week's work for the client (the post does not say which); your usual recap format or an earlier recap to follow; your own read-through and clean-up of each draft before it goes to the client.
Draft this week's recap email to [client name]. Cover what we did for them from [date] to [date], what is in progress and what we need from them next. Use [where the week's work is recorded: notes, a task list or a folder I give you] and my last recap, [paste or attach], as the format and tone to follow. Where you are unsure whether something happened, mark it 'check' instead of stating it. Do not send anything to the client; give me the draft to review and edit.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with 12 months of your bank and payment-processor charges (the thread does not say whether by connection or by export); your own review of every finding and every cancellation or switch before you act.
Review the last 12 months of charges in [Revolut and Stripe: connected access, or the exports I give you]. List every recurring charge and fee by vendor with its yearly total, keeping each currency separate. Flag: fees on payments that came in by bank transfer; subscriptions that overlap or look unused; renewals that went up; and tools with a cheaper or free alternative, naming the alternative and its price with a link, or 'unverified' if you cannot check. Show the numbers behind every line and write 'unknown' instead of guessing. Do not cancel, change or pay anything and do not contact any vendor; give me the list for my review.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; access to your list of overdue invoices (the post does not say how); a Google Sheet of customer names and contact names; your own reminder email template; access to your mailbox so drafts can be saved; your own review before anything is sent.
Every Monday evening, open [my receivables or invoice system] and list invoices that are past due. Match each customer against my Google Sheet [name] (customer name, contact name). For each match, draft a late-invoice reminder from my template [paste template], using the contact name and each overdue invoice's number, amount and due date. Save the drafts in my Drafts folder. Do not send any email. Then give me a short report: customers included, amount owed per customer and the total, plus any overdue customer who is not in my Sheet and anything you could not read. Do not change or mark anything in the invoice system; I review and send the drafts myself.
Have Grok Bot build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive, as the author says he did to replace his construction-management software.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your QuickBooks, email and OneDrive (the post does not say how it was connected); the estimate and job-cost categories your current software uses, ideally with a sample from one job; your own review of the tracker and of anything the bots prepare.
I want an estimate and job-cost tracker to replace [current software or spreadsheet]. Build it as a workbook saved in [OneDrive folder] with: an estimate sheet per job ([line items and cost codes]), a bills and actual-cost sheet per job, and a summary of budget against actual cost per job. Fill the cost data from QuickBooks ([company file]) and from bill emails in [mailbox or label], read-only: do not change anything in QuickBooks, send any email or delete anything. Match each bill to a job and cost code, and list the ones you cannot match, with the reason. First show me the structure and a sample for [one job] before you fill in the rest. For draws: when I ask, prepare the draw package for [job], draw number [n], using only invoices that were not in earlier draws, and list any issues from the last draw request. Save it as a draft and write a draft email to [bank contact]. Do not send anything to the bank; show me the package and the draft first.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your Beehiiv and Substack accounts (the post does not say how); your logo file and the text for your About page and welcome email if you want them used; your own review of the Substack site before anything is published; you cancel the old plan yourself.
Move my blog from [Beehiiv publication] to [Substack publication]. First list every post and page on Beehiiv with title, date and URL, and show me the list. Then recreate each post on Substack as a draft, keeping the wording, formatting and links; build a homepage and an About page using [text or the existing About page]; add the logo from [file]; and write a draft welcome email from [text]. Give me a checklist of anything that did not carry over or changed (for example links, embeds and URLs). Do not publish anything and do not cancel, downgrade or delete anything on Beehiiv or anywhere else; I will review the Substack site first.