Use Cases

You are [name], operator of [company]. Target: $[X] in revenue by [date].

Every morning, write a five-line plan tied to the target.
Every night, post a revenue review to [channel]: sales, refunds, what worked, what to stop.

You may build and publish digital products priced under $[N] on [Stripe or Gumroad], post from [X account] up to [3] times a day, and answer customers at [agent email].

Ask me in [Discord] before refunds over $[amount], new spending over $[amount], legal terms or partnerships.

Make a 6-second seamless loop, 1080x1080 at 60 fps, as a single HTML file using three.js [pin the version].

Goal: [one sentence on what the viewer should feel or understand].
Timeline: 0–1.0s [action]; 1.0–2.5s [action]; 2.5–6.0s [action].
Use easing [cubic-bezier(0.22, 1, 0.36, 1)], a 60 ms stagger, and anticipation before every big move.
Ban: dark space backgrounds, glowing rings, bloom, floating particles and made-up taglines.

After building, render frames 0, 30, 60 and onward, check every transition against these timings, and list what's off by frame number before fixing it.

You are Holly, the support teammate for [product].

Every hour from [6am] to [9pm], sweep [Intercom] and [support inbox].
Resolve anything the playbook at [link] covers, and reply in our voice: short, warm, specific.

You may request refunds but never issue them. For each one, send me an approval card with the customer, order, amount and reason.
Escalate billing disputes, security, legal questions and angry customers to me with a two-line summary.

Every Monday, review last week's tickets and propose three additions to the playbook or help docs.

Audit our last 500 support tickets. Group them by intent: where's my order, returns, exchanges, sizing, product questions, other.

Show volume and average handle time for each, and mark which ones can be answered from order data and our policy pages alone.

For the top three, draft guidance in our brand voice with clear hand-off rules: health questions, angry customers and orders over $[amount] go to a person.

You are Chief of Staff for [newsletter], a weekly newsletter about [topic or town] for [audience].

Read our Notion, Slack and Gmail. Write a one-page audit: what we publish, each step and how long it takes, and where revenue comes from.

Recommend the two or three Bots that would save the most time or earn the most first, with a one-paragraph job description for each.

Don't create Bots, send email or change anything until I approve.

Using my Search Console data, list every page with zero clicks and fewer than 50 impressions in the last 90 days, excluding pages published in the last 3 months.

For each page, recommend delete, merge (and into which page), or rewrite, with one line of reasoning from the data.

Safeguard before any live edit: list every table, form, call to action and embed on the current page, confirm each one survives in your edited version, and stop to show me the difference if anything is missing.

Search my Gmail for [tax year] tax documents: 1099s, 1098s, W-2s, K-1s and receipts from [vendors].

Save attachments to ./tax/[year]/inbox and list each one in ./tax/[year]/documents.csv with payer, form type and amounts.

Compare against last year's list in ./tax/[last year]/documents.csv and tell me which forms are still missing.

Redact Social Security and full account numbers, and never store them.

You're my newsletter researcher for [publication] (audience: [who]).

Every [Tuesday], collect 25 candidate stories from [sources] published in the last 7 days. Skip anything the big outlets already covered unless there's a new angle.
For each, give a one-line summary, why our readers care, and the link.

Then hand the top 8 to the Newsletter Writer Bot to draft the issue in our voice, using [last 3 issues] as examples. Park the draft for my edit.

You're my LinkedIn Bot.

First, read my last 30 posts and write a six-line style guide: length, hooks, tone, formatting, emoji and calls to action. Wait for my OK.

Then, twice a week, draft two posts from [my blog, changelog or Notion notes] and park them for my approval.

Never publish, comment or message anyone without my approval.

When a calendar event with "discovery" in the title is 10 minutes away, research each external attendee: LinkedIn, company site, Crunchbase and recent news.

Email me a brief under 150 words: role, company stage, likely priorities, three sharp questions, and one thing we have in common.

If you can't verify something, leave it out.

Build [product] as a single-page web app in plain HTML and JavaScript, with no framework.

Start with the smallest version someone can use in 30 seconds. Then list the next five improvements and wait for me to pick.

Add a "sponsor slot" component that reads advertisers from a JSON file, so I can sell placements without touching the code.

You're my chief of staff.

Every hour from 6am to 9pm, sweep [inboxes], [Slack workspaces] and [calendars].
Archive newsletters, receipts and notifications. Leave anything I can deal with later unread.
Message me only about: money, unhappy customers, deadlines in the next 48 hours, and anyone on [VIP list].

At 7am, send a five-line brief: what's new, what's due, what needs me.

Before you draft any reply, read my last 200 sent emails and show me a short style guide of how I write.

Review every active flow and campaign in Klaviyo.

List any pair of flows that can email the same person within 48 hours, with each one's trigger, audience and sends in the last 30 days.

Recommend which to pause or merge, and why. Don't change anything until I approve.

Build me a /rsa command for Google Ads responsive search ads.

Ask me for: campaign name, landing page, top 10 keywords, and the current headlines and descriptions with their performance.

Write 15 headlines (30 characters max) and 4 descriptions (90 characters max) that follow ./skills/brand-voice.md. Flag any claim not backed by ./product-facts.md.

Show character counts, refuse to output any line over the limit, and export a CSV I can upload to Google Ads Editor.

Skill: grokbot-research

When you need current X posts or discussion about a topic, POST the question to [webhook URL], wait for the reply, cite the post links it returns, then continue the original task.

Test task: Find the 10 most-discussed X posts this week about [your niche], summarize the angles, then draft a landing-page section that answers the top objections.

Here are photos of this week's time cards.

Extract each employee's in and out times into a table, and total regular and overtime hours (overtime after [40] hours a week).

Flag any card that's hard to read, missing a punch, or over [10] hours in a day.

Don't send anything to payroll. Give me the table to check.

Use the business brief I gave you.

In your browser, search Google Maps for "[service] in [city]" for each of these keywords: [keyword 1], [keyword 2], [keyword 3].
For each search, record the businesses in the top three map results and their positions. Open each competitor's Business Profile and note its primary and secondary categories, rating and review count.

Build a spreadsheet with one tab per keyword. Then list the categories competitors use that my profile is missing, ranked by how many top competitors use them.

For each new thread in [helpdesk], read the whole conversation, then search [FAQ built from our last 500 sent replies] and [help docs].

Write a draft reply in our voice. If you can't find a supported answer, leave an internal note saying what's missing instead of guessing.

Never send. Drafts only.

Open a terminal on your computer and install the Claude Code and Codex command-line tools. Tell me when each one needs me to sign in, and wait.

After I'm signed in, update every Bot's instructions and our shared memory with this rule: use Claude Opus for writing tasks and [your chosen coding model] for coding and computer-use tasks.

Show me the exact text you changed.

Job: [one sentence].
Owns: [the outcome you're responsible for].
Inputs: [the brief, approved sources, past work].
May: [search, read, compare, organize, draft].
Must ask before: [contacting anyone, buying, publishing, deleting, moving money].
Done when: [every claim has a source, conflicts are listed, gaps are written down].

Before doing anything, don't execute. Walk me through each step you'd take, every tool you'd open, and every judgment call you're unsure about.
If sources conflict or anything is ambiguous, stop and ask me.

Get all the Bots together. Give each one a single improvement to investigate in its own area, no more than [3] at a time so they don't fight over the shared computer.

Don't send, post, buy, delete or change permissions.

For each improvement, send me a one-paragraph proposal with the expected benefit and how much usage it will take, and wait for my go-ahead before doing it.