The Grok Bot directory

Set up a new bot for me I can trigger for account growth, in its own dedicated chat. Walk me through connecting X, then configure it: review my niche and recent posts, suggest a consistent schedule of original takes, visuals, and questions that spark replies, identify relevant larger accounts to engage with genuinely, track which topics and formats perform, and recommend what to double down on. Ask me my main topic, audience, voice, posting frequency, and boundaries for engagement, draft the first week of posts and replies for my approval before anything is published, then save it for a weekly planning run.

Set up a new bot for me whose only job is to create and manage my other bots. Configure it: when I describe something I want automated, it interviews me, drafts the new bot's instructions, schedule and connections, and creates it; when an existing bot is noisy or missing the mark, it tightens the instructions; and it keeps a roster of what I run and what each bot is for. It never deletes a bot without my say-so. Ask me what bots I already have and what I'm trying to get out of them, have it design its first bot with me, then save it.

Set up a new bot for me dedicated to one strategic account, in its own chat. Walk me through connecting Slack, Gmail, Gong and Granola, then configure it: watch the Slack channels for the account, digest its calls, emails and threads as they happen, flag every feature request that comes up on calls, keep me updated on its open support tickets, and tell me when we ship something relevant to this customer. When I ask it anything about the account it answers from that running context. Ask me which account, which channels and where our tickets live, let it catch up on the last month of history so I can quiz it, then save it — and I'll clone it for my other top accounts and prospects.

Set up a new bot for me I can trigger for an email cleanout, in its own dedicated chat. Walk me through connecting Gmail, then configure it: review my inbox, identify newsletters, promotions, stale threads, and other messages I no longer need, group the recommendations by type, and prepare deletions, archivals, and unsubscribe actions. Show me the full list and proposed actions before it changes anything, and require my approval before deleting messages, unsubscribing, or sending any email. Ask me what must never be touched, how far back to scan, and which senders or categories to preserve, run the first cleanout with me watching, then save it for a recurring schedule I choose.

Set up a new bot for me I can use as a single front door for managing my bot team, in its own dedicated chat. Walk me through connecting my existing Grok Bots, then review what I do and the relevant public information about me, inspect each bot's purpose and current setup, and create a clear job description and routing plan for the team. Recommend which bots to keep, rename, change, combine, or add, while avoiding duplicate ownership of tasks and opening a specialist only when its lane is needed. Show me the proposed team structure and every change before you edit, delete, create, or reassign any bot. Ask me which responsibilities are most important, which bots or workflows are sacred, what work should stay behind the front door, and how often I want the team reviewed, run a supervised first review with me, then save it for on-demand use and a regular team check-in.

Set up a new bot for me that runs my X account as a team of five agents. Walk me through connecting X, then configure the crew: an Ideator that scans X, Hacker News, GitHub and Reddit for what's about to pop off and hands me the angle early; a Hook Writer that turns each idea into a ready-to-post hook in my voice; a Planner that runs my content calendar so I always know what ships next; an Analyst that lines my followers, views and engagement up against the competitors I'm quietly tracking; and a DM Manager that watches who's talking about or mentioning me so nothing slips past. Everything is drafts and reports — nothing posts or replies without me. Ask me for my niche, my competitors and twenty of my best posts so it learns my voice, run one day of the crew, then save it.

Set up a new bot for me to act as my chief of staff, always on. Walk me through connecting Slack, Notion and Linear, then configure it: everything comes to you first, route work to the right specialist bot, keep a running list of what's in flight, and post one daily check-in about what needs a human decision. Ask me which specialist bots I already run and which channel to post in, then save it.

Set up a new bot for me that thinks about the long game on X, separate from my reply and article bots. Walk me through connecting X, then configure it: watch my interactions and the accounts around me and report on who's worth paying more attention to, how to turn casual interactions into actual relationships, which content themes fit my background, and opportunities I'd otherwise miss. It advises only — it never replies or posts for me. Ask me about my background and what I want out of X, send one strategy memo so I can see if it surfaces people I'd have missed, then save it.

Set up a new bot for me I can trigger for a cleanout. Walk me through connecting Gmail, then configure it: scrape my receipts into a list of every subscription I'm paying for with price and last use, cancel the forgotten ones I approve, and unsubscribe me from the newsletters I never open. Show me the full list with its cancel/keep recommendations before it touches anything. Ask me what's sacred, do the first cleanout with me watching, then save it for a quarterly run.

Set up a new bot for me that finds its own job. Walk me through connecting Slack, Notion, GitHub and Linear, then let it inspect my history across all four: find the repetitive work I do without noticing, and propose two automations — what triggers, what runs, what I'd save — without me describing anything first. Ask me only what it can't infer, write both proposals up for my review, then save the one I pick as its first real task.

Set up a new bot for me I can trigger when my priorities change. Review my current goal, active projects, available specialist agents, and their responsibilities, then recommend the best team structure and suggest which agents to add, remove, or reassign. Ask me about the outcome I am pursuing, the skills and agents I already have, and which changes require my approval; run the first recommendation as a dry run without changing anything, then save it as a bot.

Set up a new bot for me. Walk me through connecting GitHub, DataForSEO and Google Search Console, then schedule it every 2 weeks: find pages losing impressions or sitting on page two, rewrite titles and metadata, fix internal links, and open a PR I review before merge. Ask me for the repo and content directory, do one dry run, then save the schedule.

Set up a new bot for me in its own dedicated chat to run a local SEO team. Walk me through connecting Grok, then create five roles—Head of SEO, Keyword Research, Tech SEO, Content Writer, and Link Builder—and configure them to collaborate on a project brief. Have Keyword Research lock the exact primary terms and service-plus-town titles, have Content Writer draft the homepage and service pages with genuine local, hire-intent copy, have Tech SEO check the site structure and metadata, and have Link Builder focus first on accurate local citations and then a small, relevant backlink campaign for the homepage and service URLs; never create doorway pages, invent services, or prospect for a business that is not real. Ask me for the business name, domain, verified services, service areas, NAP details, priorities, and any claims or wording that are off limits, run the first brief and drafts with me watching, show me every page, citation, outreach target, and proposed publication or send for approval before anything goes live, then save it for on-demand SEO projects.

Set up a new bot for me I can trigger for video and content ideas. Walk me through connecting YouTube and Google Trends, then configure it: study my existing content, audience, and relevant trends, generate a steady stream of distinctive video and content concepts, and rank them by fit, novelty, likely audience interest, and ease of execution with a hook and brief outline for each. Ask me about my niche, goals, audience, preferred formats, boundaries, reference creators, and whether I want evergreen or timely ideas, do the first ideation session with me watching, then save it.

Set up a new bot for me that runs daily. Walk me through connecting X, then configure it: look at what's resonating on my timeline and in my own posts, cross it with the topics I actually care about, and send me a short list of potential longer posts I could write today — just enough to take the friction out of deciding what to write. It drafts nothing and publishes nothing. Ask me for my themes and background so the ideas fit me, send one briefing so I can judge the signal, then save it.

Set up a new bot for me I can trigger whenever I publish new source material or run weekly. Walk me through connecting YouTube, ClickFlow, Google Analytics 4, Ahrefs, and Google Search Console, plus my sales-call, customer-call, and podcast recordings, then configure it: identify the topics and formats that perform best, combine those insights with search rankings, traffic, keyword opportunities, and technical recommendations, and turn them into optimized article drafts in my CMS. Ask me which audiences, topics, keywords, brand rules, content formats, and CMS workflow matter, show me the first content and recommendations in a dry run, and require my approval before anything is published. Then save it.

Set up a new bot for me called HyperGrok Trading Desk. Follow https://github.com/galleonlabs/hypergrok-trading-desk/blob/main/SETUP.md from top to bottom: clone the repository, create the seven specialist Bots—Desk Lead, Market Analyst, Research Analyst, Strategist, Risk Manager, Execution Trader, and Trade Reviewer—install the sixteen shared skills, and create the Trading Floor group chat with the first six (the Trade Reviewer works by DM). Walk me through connecting GitHub so you can fetch the desk files and Hyperliquid starting in research mode with no keys and no orders, then a trade-only API wallet on testnet before any mainnet wallet. Ask me for engagement level (research, testnet, or mainnet), the Hyperliquid account address the desk should read if I want live state, and my written risk limits. Run the five read-only verification checks from SETUP.md with me watching, never send an order without my explicit approval by ticket id, then finish with the receipt SETUP.md asks for and save the desk.

Set up a new bot for me I can trigger for Bible study. Walk me through connecting a Bible text or study resource and web search, then configure it: answer my questions by citing the relevant passages, clearly separate direct scriptural teaching from interpretation or tradition, compare translations when useful, and flag uncertainty instead of presenting speculation as fact. Ask me which translation, books, languages, and interpretive traditions I prefer, do a supervised first study with me, then save it.

Set up a new bot for me to be my digital Marie Kondo. Walk me through connecting Gmail, then configure it: clean up my inbox — archive the clutter and unsubscribe me from what I never open — and find every paid subscription in my receipts so I can see what I'm spending and cancel what no longer sparks joy. Show me the full list of what it wants to archive, unsubscribe and cancel before it touches anything. Ask me what's sacred, do the first cleanout with me watching, then save it for a regular run.

Set up a new bot for me that acts as my iCloud bridge. Walk me through signing into iCloud in your browser and keeping that session alive, then configure it: when my other bots need my contacts or reminders and there's no MCP for it, they ask this bot, and it reads or updates through the browser and passes the answer back. Ask me which bots get to use it and whether anything is read-only, run one lookup end to end so I can see the handoff, then save it.

Set up a new bot for me that runs a morning portfolio briefing. Walk me through connecting Plaid for my holdings and balances, Yahoo Finance for live prices and market data, and Google Calendar for upcoming market events, then configure it to check overnight moves each morning, summarize the biggest changes, surface relevant events, and flag positions that may warrant rebalancing based on my rules. Ask me which accounts and assets to include, my risk tolerance, target allocations, rebalance thresholds, timezone, and which events matter most, run the first briefing with me watching, show me every rebalance recommendation before I take any action, then save it for a daily run.

Set up a new bot for me that runs my grocery ordering, in its own dedicated chat. Walk me through signing into Amazon and Costco in your browser and connecting Google Calendar, then schedule it weekly: plan the week's meals, order bulk goods and frozen staples from Costco and fresh produce and everything else from Amazon, and put what to cook and when on my calendar. Remember every preference I mention along the way — "no olives" should stick forever. Ask me for my staples, dietary rules, budget and delivery windows, hold each order for my approval until I say otherwise, then save it as a bot I can edit later.

Set up a new bot for me in its own dedicated chat that resolves disagreements between my Grok bots. Walk me through connecting the bots and their conversation histories, then configure it to detect conflicting claims, plans, or recommendations, compare the evidence and assumptions behind each position, ask the relevant bots for clarification when needed, and produce a reasoned resolution or clearly escalate the unresolved conflict to me. Ask me which sources and bots should be trusted, what criteria define an acceptable resolution, and when I want to be interrupted, run the first conflict review with me watching, then save it for use whenever disagreements arise.

Set up a new bot for me I can trigger for a mail cleanout. Walk me through connecting all of my Gmail and Outlook accounts, then configure it: scan messages and receipts, classify them by priority and focus, identify newsletters and recurring senders I do not read, and prepare targeted unsubscribe and filing actions, aiming to remove roughly 90% of low-value mail without losing important messages. Ask me which senders, subjects, accounts, and categories are sacred, how I define urgent mail, and which labels or folders to use, do the first pass as a dry run, show me every unsubscribe and filing recommendation before it touches anything, hold all unsubscribes and moves for my approval, then save it.

Set up a new bot for me I can trigger for a subscription audit, in its own dedicated chat. Walk me through connecting Gmail, then scan receipts, invoices, and billing emails to find every subscription I am paying for, including its price, billing frequency, merchant, and recent evidence of use, and tell me which ones I should consider cancelling. Ask me what services are essential, which household or work subscriptions I share, and what savings threshold matters to me, do a supervised first audit, then save it for a monthly run. Do not cancel anything unless I explicitly approve a specific subscription later.

Set up a new bot for me that researches a topic on YouTube. Walk me through connecting YouTube, then configure it to scan the top relevant videos for a topic I provide, rank the strongest sources, review their titles, descriptions, transcripts, and engagement signals, and produce a concise research brief with the main claims, areas of agreement and disagreement, useful timestamps, and links back to the videos. Ask me what topics and channels to prioritize, how many videos to review, which freshness and credibility signals matter, and what format I want for the brief, run one topic as a supervised trial, show me the sources and draft findings before sharing anything, then save it for on-demand research.

Set up a new bot for me that manages a team of development bots in an engineering group chat. Walk me through connecting Linear and GitHub, then configure it to maintain 5–10 focused developer bots in an engineering section, accept a shared outcome or set of tickets from me, identify which bots are available, divide the work into non-overlapping requirements, assign tasks, let the bots hand off context and results to one another, and report blockers, progress, tests, and pull requests back to me. Ask me what each bot should specialize in, which repositories and Linear projects they may use, how to prioritize work, and which actions require review. Show me the proposed assignments and handoff plan before posting tasks to the group, and require my approval before merging changes, opening public-facing updates, or sending messages outside the engineering group, then save it.

Set up a new bot for me I can trigger for a bookkeeping audit. Walk me through connecting my bookkeeping system, bank and credit-card records, and check images, then configure it: audit the books, inspect check images, reconcile credit-card transactions, identify discrepancies, and review transactions for potentially deductible business expenses and tax write-offs. Produce an exceptions report with supporting evidence and recommendations, and never edit the live books or classify, delete, or submit anything until I approve each change. Ask me which accounting period, entities, tax jurisdiction, chart of accounts, and expense rules to use, do a supervised dry run on a sample period, then save it for a recurring audit.

Set up a new bot for me I can trigger with a podcast episode or feed, in its own dedicated chat. Walk me through connecting my podcast sources, then configure it: retrieve or create a transcript, summarize each episode in the context of what I work on, highlight decisions, claims, and actionable ideas, and include the raw transcript and source links so I can verify everything myself. Ask me what topics and projects matter, how long the summaries should be, which sections I want, and whether I prefer summaries on demand or on a schedule, run the first episode with me watching, then save it.

Set up a new bot for me I can trigger whenever my faceless channel needs a short. Walk me through connecting AITuber at https://mcp.aituber.app and linking my YouTube and TikTok channels inside it so it can publish for me (https://aituber.app). Then configure it: pull topic ideas for my niche, drop the ones close to videos already in my library, expand the best one into a narration script at my target length, check what the run costs against my credit balance, and generate it with the template, voice, image style, caption style, and music I chose. When it finishes, export it and publish with a title, description and tags for YouTube and a separate caption for TikTok. Ask me my niche, length, template, voice, visual and caption style, posting time, and the claims it must never make. Show me the ideas, the script, and the finished video before anything goes out, then save it.

Set up a new bot for me in its own dedicated chat that acts as the front door to my agent team. Let me describe a goal or task in plain language, determine which specialist agent should handle it, pass along the relevant context, track the result, and bring the completed work back to me. Ask me which agents exist, what each one is responsible for, what information they may share, and when I want to review a proposed delegation before it runs; test the first delegation with me watching, then save it as a bot.

Set up a new bot for me that watches my inbox for flight confirmations. Walk me through connecting Gmail, then configure it: track each flight's check-in window, check me in the moment it opens with my usual seat preference, and ping me only when it hits a 2FA prompt or captcha that needs a human. Ask me for my airlines, loyalty numbers and seat rules, walk through one upcoming flight together, then save it.

Set up a new bot for me in its own dedicated chat that acts as my SaaS chief of staff. Walk me through connecting Gmail, Google Calendar, Slack, and Discord, then configure it to give me a morning summary at 5am each day covering important messages, meetings, commitments, and open work while flagging fires that need putting out. Ask me which people, projects, channels, senders, and urgency rules matter, run the first briefing with me watching, and require my approval before it sends messages, changes calendar items, or takes any external action; then save it for a daily run.

Set up a new bot that tells me when competitors make meaningful changes to their websites. Walk me through connecting ScreenshotOne and Slack, then ask which competitors and which homepage, product or pricing pages I care about and how often to check them. Capture a baseline for each page. On future runs, ignore layout noise and rotating content, and alert me only when a competitor changes its pricing, packaging, features, positioning or calls to action. Show me exactly what changed, include before-and-after screenshots and add one sentence on why it may matter. Run one check with me, then save it.

Set up a new bot that persists knowledge from my bots to one GitHub repo. Chat memory dies when the thread ends. Decisions, preferences, and what shipped get trapped in transcripts nobody searches. A git repo is the durable record: versioned, searchable, and shared by every bot I run. Walk me through connecting GitHub. Ask me for the repo, my timezone, which bots should write, and a daily write time. Then set it up like this: - One folder per bot. - Each bot writes one markdown file per day (`YYYY-MM-DD.md`). - Log only decisions, shipped work, and standing preferences. - Never log secrets, tokens, passwords, customer data, or private messages. - If nothing happened that day, stay quiet. - If the GitHub connector cannot see a private repo, write through the GitHub contents API with the stored personal token and never print it. Do one supervised first write I approve, then save the daily schedule.

Set up a new bot for me that scouts X for me. Walk me through connecting X, then configure it: find the viral and genuinely funny tweets in the topics I follow and send me a short list with the link, the author, why it took off, and anything I could riff on. It reads only — it never posts, likes or replies from my account. Ask me for my topics and how often I want a batch, send one so I can tell it what to keep and drop, then save it.

Set up a new bot for me I can trigger whenever I need a fresh ad. Walk me through connecting MaxFusion at https://mcp.maxfusion.ai/mcp (https://maxfusion.ai), then configure it: ask me for my product name and URL, two or three product photos, who buys it, three to five competitor brands, the promise I am allowed to make and the claims I am not. Search the Meta Ad Library for each competitor's video ads and keep the ones that have been running longest, since the survivors are the ones making money. Transcribe the top five to eight and break each one down into hook, structure, the objection it handles and the call to action, then show me that table. Pick the strongest angle and write one 30-second yapper-style script for my product on it: spoken word for word, about 80 words, hook in the first two seconds, one objection, one proof beat, a soft close, no competitor names and nothing from my banned claims list. Turn it into a Seedance 2.5 prompt: one creator talking to a handheld selfie camera in a single continuous take, the script verbatim as the spoken line, my product held up and named on screen, my photos attached as image references and one or two of the competitor ads attached as video references for pacing only, portrait, 30 seconds, 720p for the draft. Show me the table, the script and the full prompt and wait for my go before spending credits. Generate one clip and hand it back with the script and prompt behind it, so a near miss is fixed by changing one thing. When I say a clip won, keep the angle and the creator and write the next script from it, then save it.

Set up a new bot for me that audits a codebase that shipped fast and now needs hardening. Walk me through connecting GitHub, then configure it: given a repository, work through this fixed 20-point checklist in order — duplicate utility functions, secrets committed in config files, functions over 400 lines, components over 200 lines, dead code, silent or empty catch blocks, API calls in the UI missing loading/error states, database queries written directly in route handlers, synchronous I/O in request handlers, list endpoints with no pagination, inconsistent API response shapes, floats used for money instead of integer cents, dates stored as plain strings instead of ISO 8601, external calls with no retry/backoff, stale comments that no longer match the code, unvalidated user input, API routes missing auth checks, missing indexes on frequently queried columns, N+1 queries, and third-party SDKs initialized in more than one place. For each check, search the codebase, list every finding with its file and line, and either apply the fix or propose it clearly — report "none found" rather than skipping a check, never omit one. Finish with a summary table showing fixed / proposed / none-found across all 20 checks, and always ask before making any sweeping change that touches many files. Ask me which repository and branch to run against and whether it may open pull requests directly or must hand me a diff to review first, do a dry run against a repo I point you to, then save it.

Set up a new bot for me I can trigger each morning for an email briefing. Walk me through connecting Gmail, then configure it: review my inbox, sort messages by urgency, summarize the important threads in a concise brief, and draft replies to the messages that need an answer. Keep every reply as a Gmail draft and never send anything automatically. Ask me which senders and topics are urgent, what tone to use, and which messages should always be left alone, do a supervised first run with me reviewing the brief and drafts, then save it for a daily run.

Set up a new bot for me I can trigger with a topic. Walk me through connecting X, then configure it: scrape recent tweets on the topic into a CSV with exactly the columns I ask for — author, followers, link, claim, sentiment, whatever the run needs — one shot, no babysitting. Ask me for a topic and my default columns, run it once so I can check the output opens clean in a spreadsheet, then save it.

Set up a new bot for me I can trigger when a project needs AI clips. Walk me through connecting AITuber at https://mcp.aituber.app (https://aituber.app), then configure it: turn my brief into a numbered clip list, and for each clip pick a model that can actually shoot it — read what each one supports for aspect ratio, resolution, length, sound, and a start and end frame before choosing, and attach my reference images or saved elements when a clip has to match a look. Price the whole set first. Then generate, hand the clips back in list order, and keep the prompt, model and settings behind each one so a near miss is regenerated by changing one thing instead of rewriting it. Ask me the aspect ratio, resolution, clip length, whether I want sound, and my credit ceiling per batch. Show me the list, the models and the total cost for approval, run one batch with me watching, then save it.

Set up a new bot for me that runs daily. Walk me through connecting the Bot Directory API using its documentation, then configure it to fetch newly added bots once a day, identify the ones that match my interests, explain why each is interesting, and prepare the selected bots for creation. Ask me which categories, capabilities, and quality signals matter to me and whether I want automatic or conservative recommendations, show me the full list and proposed creations for approval before creating anything, do a supervised first fetch and dry run with me, then save it for a daily run.

Set up a new bot for me I can trigger each morning for a daily focus plan. Walk me through connecting Google Calendar, then configure it: review today's commitments, my current projects, deadlines, and unfinished priorities, recommend the most important work for today, and turn it into a realistic sequence of focus blocks with a short explanation of what to defer. Ask me about my goals, immovable commitments, preferred working hours, and what kinds of work deserve priority, do a supervised first plan with me, then save it for a daily run.

Set up a new bot for me I can trigger when my profile goes stale. Walk me through connecting my LinkedIn session, Notion and Slack, then configure it: audit my live profile against what I actually do now — pulling context from my notes and recent messages — and rewrite the headline, about section and experience bullets in my voice. Nothing publishes without my approval. Ask me who I want the profile to speak to, show me a full draft side by side with the current version, then save it.

Set up a new bot for me as my personal travel concierge. Walk me through connecting Gmail so it can read my booking confirmations, then configure it: when I give it a trip, research the flights and stays that fit, look for the cheaper options I'd miss — better fares, alternative dates or airports, price drops on what I've already booked — and tell me exactly how much each would save. Nothing gets booked, changed or cancelled without my approval. Ask me my home airport, budget and dealbreakers, run it on a trip I'm actually planning, then save it.

Set up a new bot for me I can trigger to write YouTube scripts. Walk me through connecting YouTube and Google Docs, then configure it: turn a topic or approved video idea into a complete script with a strong opening hook, logical sections, spoken-word narration, transitions, examples, visual or B-roll suggestions, and a clear ending, then save the draft as a text document for my review without publishing it. Ask me about my audience, channel voice, target duration, pacing, research standards, recurring segments, and topics to avoid, do the first script with me watching, then save it.

Set up a new bot for me I can trigger for accounting work on a schedule, in its own dedicated chat. Walk me through connecting Notion for my accounting notes and records, then configure it: perform the recurring accounting tasks I specify, organize the results into clear records and summaries, flag missing or unusual items, and keep a running history so I can gradually add more accounting tasks over time. Ask me which tasks to run, what sources and categories to use, how often to run them, which thresholds should be flagged, and what outputs I need, show me a supervised dry run before changing or recording anything, require my approval for any financial action or outward communication, then save it for the agreed schedule.

Set up a new bot for me in its own dedicated chat that continuously improves my Google Ads account. Walk me through connecting Cursor and Google Ads, then configure a scheduled daily manager that reads unified campaign and conversion data, evaluates search-term intent on a 1–10 scale for whether each query indicates someone wants to buy my product, adds appropriate negative keywords, and recommends or applies other account optimizations while tracking cost per qualified demo and downstream lead quality rather than conversion volume alone. Ask me how I define a qualified demo, which outcomes or closed-revenue signals should count, my budget limits, targeting constraints, and which changes require review. Show me the proposed changes and expected impact before anything that changes targeting, bids, ads, or spend, run the first optimization as a supervised dry run, then save it for daily execution.

Set up a new bot for me I can trigger each morning for household coordination. Walk me through connecting Google Calendar and Apple Messages, then configure it: check family calendars, events, kids' grades and school schedules, identify follow-ups for teachers and volunteers, and prepare a prioritized list of what needs attention. Draft texts and messages for me to review, but hold every message until I explicitly approve it. Ask me which calendars and schools matter, who may be contacted, what follow-ups are time-sensitive, and what tone to use, do a supervised first review with me, then save it for a daily run.

Set up a new bot for me I can trigger to create short-form content. Walk me through connecting YouTube and CapCut, then configure it: review my source videos, identify the strongest moments, cut them into concise vertical Shorts with hooks, captions, titles, descriptions, and suggested posting times, and show me every finished cut before it is published. Ask me about my audience, voice, acceptable editing style, target platforms, preferred length, and topics to avoid, do the first batch with me watching, then save it.

Set up a new bot for me to act as my chief of staff for enterprise sales, and pin it. Walk me through connecting Salesforce, Gmail, Google Calendar, Slack and Granola, then configure it: it owns my meeting prep, my inbox and my post-call drafts, and it orchestrates the rest of my bots — spinning up new specialist bots when a job needs one, calling my slides bot for decks, and organizing my bots into sections. Every so often it reviews all my bots and routines and tells me what to automate, parallelize or clean up. Nothing sends or changes in Salesforce without me. Learn how I write from my sent mail and Slack first, ask me which bots I already run and what I want on my phone during the commute, then save it.

Set up a new bot for me I can trigger for website design work, in its own dedicated chat. Walk me through connecting Figma and Squarespace, then configure it: turn my brief into page structures, wireframes, visual directions, responsive layouts, and implementation-ready design notes, while keeping changes safe and never deleting or publishing anything without my approval. Ask me about my brand, audience, accessibility requirements, preferred references, existing site structure, and what is sacred, do a first page design with me watching, then save it.

Set up a new bot for me that researches YouTube. Walk me through connecting YouTube, then configure it: in the niches I care about, find the outlier videos — the ones performing far above their channel's usual numbers — and send me a list with the title, channel, views versus that channel's baseline, and what the video did differently. Ask me for my niches, a few channels I already track, and how often I want the list, run one search so I can check the outliers are real, then save it.

Set up a new bot for me in its own dedicated chat that verifies the work of my Grok bots for factual inconsistencies and hallucinations before it moves to the next step in a chain. Walk me through connecting the participating bots and their outputs, then configure it to check each claim against cited evidence or reliable sources, flag unsupported statements and contradictions, explain the required correction, and return a verified or rejected result to the next bot instead of silently passing questionable work along. Ask me which source types and evidence standards to use, what uncertainty threshold should stop the chain, and who should receive escalations, run the first verification pass with me watching, then save it as a gate for every chained task.

Set up a new bot for me. Walk me through connecting my Google Calendar and Slack, then schedule it to run every weekday at 7:00am and send me one message: my calls in order, who I'm meeting and why, anything that moved overnight, and the one thing to prepare for. Ask me whatever you need, show me a test run, then save it as a bot I can edit later.

Set up a new bot for me called Firstmate in its own dedicated chat, the only agent I talk to. Walk me through configuring it in Grok and connecting Cursor Cloud Agents for delegated development work, then configure it: handle simple requests yourself when they take a single tool call, and send anything larger to an appropriate teammate bot or native agent, supervise the work, verify the result, and bring every update and final answer back to me in plain language. Keep track of delegated tasks, recover transparently when an agent or tool fails, and continuously improve the delegation workflow from my feedback. Ask me what kinds of work I want handled directly, what should be delegated, which teammates or tools are available, and what quality checks matter, run a small supervised delegation as a trial, then save it.

Set up a new bot for me that finds replies worth writing on X. Walk me through connecting X, then configure it: look for higher-signal posts in the topics I care about and draft a starting reply to each in my voice — a first take I can react to instead of staring at a blank box. It never posts anything; I rewrite and send every reply myself. Ask me for my topics, the accounts I want to build relationships with and a few replies I'm proud of so it learns my voice, show me one batch of drafts, then save it.

Set up a new bot for me I can trigger when I need to plan a trip. Walk me through connecting Google Flights, airline booking websites, and Google Calendar, then configure it: find flight options for my dates and route, prioritize aircraft and airlines with Starlink access, compare schedules, price, layovers, and baggage rules, and prepare the best option for booking. Ask me how strongly to prioritize Starlink, my budget, preferred airlines, cabin, airports, and acceptable layovers, show me the complete itinerary and price, and hold the booking for my approval before purchasing. Do the first search with me watching, then save it.

Set up a new bot for me I can trigger whenever I need help writing, rewriting, editing, brainstorming, or improving content, in its own dedicated chat. Walk me through connecting Google Docs and Notion, then configure it: accept a draft or rough idea, clarify the audience and goal, suggest outlines or alternatives, improve structure and wording while preserving my voice, flag unclear claims and errors, and return both a polished version and a concise explanation of the meaningful changes. Ask me about my preferred tone, audience, formats, recurring projects, and how aggressively I want edits made, do a supervised first rewrite with me, then save it.

Set up a new bot for me that automatically records my agents' work in ClickUp so tasks and decisions do not get lost. Walk me through connecting ClickUp, then configure it to capture each agent's task, status, important updates, decisions, links, and final output in the appropriate workspace, list, or project, while avoiding private information I exclude. Ask me how to map agents and task types to ClickUp locations, which fields and updates matter, and what should stay private; perform the first logging run with me watching and let me approve any task or update before it is created, then save it for ongoing use.

Set up a new bot for me that runs weekly for one strategic account. Before the first run, ask me which industry and product category we sell into, which topics count as signals for us, and which roles or teams at the account matter most, and save the answers. Walk me through connecting X and Slack, then configure it: search the web for new webinars, podcasts and recorded talks featuring people at the account, prioritizing the roles I named plus exec strategy interviews, and search X for recent posts from or about the company's accounts and known people there, prioritizing my signal topics and any mention of our category or competitors. Keep a state file of everything already covered so it only reports genuinely new items. For each new item actually consume it — fetch the transcript or show notes, watch the video or transcribe the audio — and give me 3 to 6 takeaways, every mention of our category and competitors with sentiment, notable quotes with timestamps, and one line on why it matters, and for X posts the author, date, text, link and why it matters. Flag anything that looks like a buying signal. Send one weekly roundup, a single line if nothing is new, and say so rather than skipping when a transcript can't be obtained. Run one rundown for the account I name, then save it.

Set up a new bot for me on a weekly schedule to audit my other bots. Walk me through connecting Slack, then configure it: go through every bot I run, tally what each one costs and what it actually produced this week, flag the wasteful ones with a kill/keep recommendation, and post the ledger. Nothing gets killed without my say-so. Ask me where my fleet lives and what a bot has to earn to stay, then save it.

Set up a new bot for me I can trigger with a photo of my fridge. Walk me through connecting Amazon, then configure it: figure out what I already have, plan a week of dinners around it, and build the cart for just what's missing, timed to the store's delivery window. The cart waits for my approval before anything is ordered. Ask me about diets, dislikes and how many I'm feeding, run one week for me to check, then save it.

Set up a new bot for me I can trigger for help making software for platform games and 3D games, in its own dedicated chat. Walk me through connecting GitHub, Unity, Godot, and Blender, then configure it: help me turn a game idea into a technical plan, write and explain gameplay code, design platforming systems, build 3D scenes and assets, troubleshoot errors, and organize the project into small testable tasks for the engine I choose. Ask me which engine and target platforms I use, my programming experience, the game concept, art and performance constraints, and how I want code and assets organized, do a supervised first prototype or debugging session with me, require my approval before modifying files or creating commits, then save it.

Set up a new bot for me. Walk me through connecting Gmail, then schedule it to check every 30 minutes: label anything genuinely waiting on my reply, ignore newsletters, receipts and cold outreach, and give me one short list, newest first, with what each person is asking for. Ask me who counts as important, run it read-only once so I can check it, then save it.

Set up a new bot for me in its own dedicated chat that builds a complete, current context brief for my marketing decisions. Walk me through connecting Gmail, Slack, Notion, Google Analytics, HubSpot, and Google Ads, then configure it to collect and organize my company background, products, positioning, customers, audiences, goals, offers, brand voice, past campaigns, performance data, sales feedback, constraints, and active experiments from those sources, flag gaps or conflicting information, and keep the context refreshed from live data on a schedule I choose. Ask me which sources and business details are authoritative, what information is sensitive, which metrics and channels matter most, how often to refresh, and what decisions I want the context to support. Do a supervised first collection and let me review and correct the resulting context brief before saving it, then save it as a bot.

Set up a new bot for me I can trigger to maintain a dedicated Notion page. Walk me through connecting Notion, then configure it: capture the notes, decisions, context, and updates I give you, organize them into the agreed sections, and keep the page current without deleting or rewriting important history. Ask me which page to maintain, what sections and formatting I want, what belongs in shared memory, and what must stay private, show me a supervised first update for approval, then save it.

Set up a new bot for me called Relationship Coach, in its own private chat. Walk me through hooking it into the Bee API so it can read what my AI pin recorded during the day, then schedule it every night at 7pm: act as a personal and couples therapist, tell me how I could have been a better partner, business partner or friend in today's conversations, and give me advice on navigating my relationships. Keep it between us — it never messages anyone else. Ask me who the important people in my life are and how blunt I want it, run it on today's recording, then save it.

Set up a new bot for me I can trigger for studying technology. Walk me through connecting web search and Google Drive, then configure it: turn a technology topic or source I provide into a structured study plan, explain concepts from beginner to advanced level, collect current references, generate practice questions and projects, and track what I have completed. Ask me which technology, my current skill level, learning goal, available time, and preferred format, do a supervised first study session with me, then save it.

Set up a new bot for me as a recurring routine. Walk me through connecting Google Calendar, Granola and Gong, then configure it: find every external call that ended since the last run — any meeting with an attendee outside my company's domains — treat the meeting notes as the source of truth, and draft a follow-up in chat with To, Subject and body, grounded in what was actually discussed, with concrete next steps. Drafts only; I send them. Ask me for my company domains and how I like a follow-up to read, draft one from my last call, then save it.

Set up a new bot for me that triggers after my calls. Walk me through connecting Google Calendar and Slack, then configure it: thirty minutes after each call ends, send me the follow-ups I committed to — who to write, what to send, what I said I'd check — so nothing slips while I'm already in the next thing. Ask me where my commitments usually live and how I want the nudge phrased, shadow one day of calls, then save it.

Set up a new bot for me I can trigger for a class-action claim search. Walk me through connecting Gmail and providing my statements and order histories, then configure it: review my emails, statements, receipts, and purchase histories, compare them with current class-action settlements and eligibility requirements, and create a report showing possible matches, deadlines, estimated claim value, and the evidence needed for each claim. Draft applications for my review but never submit a claim or share personal information without my explicit approval. Ask me what jurisdictions and purchase categories to include, which privacy boundaries to follow, and whether to prioritize claim value or low effort, do a supervised search with me, then save it for an on-demand run.

Find the signal I'm missing because it's buried across separate meetings and channels. Look across my recent conversations for a pattern that no single meeting would reveal; a concern that's coming from different people in different rooms, a topic that keeps adjacent-ly coming up, a slow shift in how something is being talked about. The thing I can't see from inside any one conversation. Tell me what's there, where it's showing up, and what you think it might mean. Connect Granola and Slack if they aren't already connected, and give me the pattern across my last two weeks of meetings and messages. When you're done, save yourself as a bot named "Find the Signal."

Set up a new bot for me I can trigger when something at home needs fixing, in its own dedicated chat. Walk me through connecting Photos, HireNimbus, Gmail, and Google Calendar, then configure it: let me send photos and a description of the issue, identify the likely job, find suitable vetted home-service professionals in HireNimbus, request and compare quotes, summarize availability and recommendations, and prepare the approved appointment and follow-up emails in Gmail and Google Calendar. Ask me about my home address, preferred service areas, budget limits, urgency, access instructions, and which repairs require especially qualified or licensed professionals. Show me the diagnosis, providers, quotes, messages, and proposed appointment before contacting anyone, spending money, or booking anything; do the first request with me watching, then save it.

Set up a new bot I can ask to investigate opportunities from Trends.vc. Use my web browser and let me sign in if needed. Ask about my skills, audience, budget and preferred business models, then browse Trends.vc with me and help me choose an opportunity. Research the live market too: competitors, pricing, recent launches, customer complaints and signs of demand or saturation. Cite direct links and clearly separate the Trends.vc thesis from your own conclusions. Deliver the case for, the case against and a seven-day validation test, then save it as an on-demand bot.

Set up a new bot for me that runs my TikTok and YouTube on a schedule without me. Walk me through connecting AITuber at https://mcp.aituber.app (https://aituber.app) and linking both accounts inside it, then configure it: build the autopilot itself with the niche or standing instructions it writes from, the frequency, time of day and timezone, and the look — template, length, aspect ratio, whether visuals are AI images, AI clips or stock footage, the voice, captions and background music — plus how titles and captions should read on each platform, the AI-generated disclosure TikTok wants, and whether comments stay open. Then keep it healthy: each week read back the runs it made and what they published, feed the topics that landed into its instructions, and tell me before a low credit balance pauses the schedule. Ask me for every setting it cannot infer, show me the whole setup and the first video for approval, then save it.

Set up a new bot for me called Blip that I can trigger for chief-of-staff support, in its own dedicated chat. Walk me through connecting Grok and illo_skill, then create and set a custom animated avatar for the bot and configure it to help me review priorities, organize my next actions, and prepare drafts or recommendations for my approval. Ask me about my role, recurring responsibilities, priorities, communication style, and what it must never do without permission, run a supervised first check-in with me watching, show me any proposed messages or actions before sending or taking them, then save it.

Set up a new bot for me I can trigger to find and track LinkedIn prospects. Walk me through connecting Google Search and a CSV file, then configure it: search Google for LinkedIn profiles that match my ideal customer profile, capture each person's name, role, company, profile link, and relevant qualification notes, remove duplicates, and maintain a CSV with outreach status, last action, next step, and notes. Do not contact anyone or automate LinkedIn activity; prepare the prospect list and status updates for my review. Ask me to define my ICP, target industries and titles, geography, exclusions, and outreach-status stages, do the first search and CSV export with me watching, then save it for on-demand runs.

Set up a new bot for me that runs before I wake up. Walk me through connecting Slack, then configure it: turn yesterday's important threads and today's priorities into a roughly three-minute audio briefing I can play from my phone while I get ready. Ask me which channels matter, what voice and pace I want, and where to drop the file, produce one episode for me to listen to, then save the schedule.

Set up a new bot for me in its own dedicated chat that orchestrates development work across multiple repositories. Walk me through connecting GitHub and Cursor Cloud Agents, then let me give it a high-level request such as adding an API endpoint and updating all related SDKs; have it identify the affected repositories, delegate coherent tasks to cloud agents, track dependencies, run the relevant tests, and summarize the resulting changes. Ask me which repositories, branches, coding conventions, test commands, and review rules to use, do a supervised trial on a small change, and require my approval before merging or deploying anything; then save it for on-demand use.

Set up a new bot for me I can trigger to find Reddit conversations where I can provide useful comments. Walk me through connecting Reddit, then configure it: search for recent, relevant posts in communities related to my topics and goals, filter out low-quality or irrelevant threads, and give me the post links with a short explanation of why each is a good fit and the value I could add. Ask me which topics, subreddits, audiences, and types of posts to prioritize, do the first search with me watching, then save it for on-demand runs.

Set up a new bot for me I can trigger to find viral, memeable stories online, in its own dedicated chat. Walk me through connecting Google News and X, then configure it to scan recent stories and trending posts, rank items by momentum, originality, visual or comedic potential, and relevance to my audience, and return a short brief with links, why each story may spread, and suggested angles without copying or fabricating details. Ask me which topics, regions, audiences, and channels matter, what makes a story memeable to me, and how recent or controversial the sources may be, run the first search as a dry run for my review, then save it for a schedule I choose.

Set up a new bot for me I can trigger to write an article or newsletter. Walk me through connecting Google Docs, Gmail, and Squarespace, then configure it: gather my source material, research only when needed, produce a clear draft in my voice with a headline, structure, links, and newsletter subject line, and show me the complete copy before sending or publishing anything. Ask me about my audience, tone, recurring themes, evidence standards, formatting preferences, and words or claims to avoid, do the first draft with me watching, then save it.

Set up a new bot for me that owns my customer decks in Figma. Walk me through connecting Figma and give it our brand system and design guidelines up front, then configure it: maintain one master deck, make a copy customized for each customer I name, and translate decks into other languages on request, always inside the brand system. Let my other bots — my chief of staff, my meeting prep bot — call it when they need a deck. Ask me for the master deck and the guidelines, have it build one customer copy for me to review, then save it.

Set up a new bot for me I can trigger for a deep business interview. Walk me through configuring it to ask structured questions about my business, goals, constraints, customers, current projects, and working preferences, then turn my answers into concise reusable context for my other agents. Ask me which facts are stable enough to retain, do the first interview with me watching so I can correct the summary, then save it as a bot.

You are my social content publisher. On the cadence I set, you turn the things I published or wrote into on-brand carousels, single images, and reels, and you queue them to my social accounts through PostNitro. You never post anything I have not seen first. **Before you do anything, set yourself up.** Ask me for whatever is missing and stop until you have it: 1. A PostNitro API key (PostNitro → Profile → Embed → Generate API Key). Use it via the PostNitro MCP server, or the CLI (`npm i -g @postnitro/cli`, then `postnitro auth set-key <key>`). 2. Where my source material comes from each week — a blog RSS/sitemap, a newsletter archive, my X account, a Notion or Google Docs folder, or "I'll paste it." Pick one; ask me to confirm the URL. 3. How often you run — weekly, biweekly, monthly — plus the day and time you fill the queue, and my timezone. 4. How many posts per run, and the platform mix (e.g. 3 LinkedIn carousels + 2 Instagram images + 1 reel). Then discover my workspace and show me what you found before you generate anything: `brand list`, `template list`, `preset list`, and `social list`. Confirm which brand kit, template, and social accounts to use, and save them as defaults (`defaults set --template-id … --brand-id … --preset-id …`) so you stop asking. Note the social-account IDs — scheduling needs them, not the handles. **Each run:** 1. Pull everything new from my source since the last run. List the candidates with a one-line angle for each, and tell me which ones you'd cut and why. Aim for the number of posts I asked for, and never repeat a topic you have already shipped — keep a running log of what went out and when. 2. For each approved item, generate the design: - Long-form article or thread → carousel. `carousel generate --context "<url>" --type article --wait` (`--type x` for an X post URL, `--type text` for a raw topic). Add `--instructions` with the audience and the takeaway I want landed. - Single stat, quote, or announcement → `image generate --context "…" --wait`. - Anything with a step-by-step or before/after shape → a reel: `video generate --context "…" --response-type MP4 --video-duration 30 --wait` (pick an `--audio-id` from `audio list`, or go silent). - When the topic is visual, add `--generate-images --image-context "<short visual brief>"`. Images are best-effort — if the result's `imageGeneration` step says it was skipped, tell me instead of silently shipping plain slides. 3. Write the caption yourself, in my voice, from the actual content — hook on line one, no "In today's fast-paced world", 2–4 relevant hashtags, and a platform-specific variant when the platforms differ enough to matter. 4. Queue it. Keep the `designId` from the generate step (not the `embedPostId`) and schedule with `--status DRAFT` first: ``` schedule create --status DRAFT --scheduled-at "<future ISO-8601 Z>" \ --design-id <designId> --selected-accounts '["<socialAccountId>"]' \ --linkedin-post-settings '{"postType":"document","postTitle":"<5–90 chars>"}' \ --post-content '{"common":"<caption>"}' ``` Instagram, TikTok, and Threads each need their own `--*-post-settings`; reels inherit their duration and audio from the design unless I say otherwise. 5. Report back: one line per post with the platform, the scheduled time, the `editorUrl`, and the caption. Ask me to approve. Only after I say yes, flip the drafts to `SCHEDULED` with `schedule update` — send the full body, since update replaces state rather than patching it. **Rules I care about:** - Space posts out across the cycle; never stack two on the same account within four hours. Check `schedule list --from … --to …` before picking slots so you don't collide with something already queued. - Every scheduled time is in the future and ends in `Z`. - If a design generates but scheduling fails, do not re-generate — the error carries the `designId`, so retry the schedule with it and don't burn credits twice. - If you run out of credits or quota, stop and tell me the exact command that failed. Don't degrade to a worse post. - Never invent a statistic, a quote, or a customer name. If the source doesn't support the slide, cut the slide. Once I've confirmed the setup, save yourself as a bot named "Carousel Publisher" running on the cadence, day, and time I gave you, with the brand, template, and account IDs baked in, and confirm the first run's date back to me.

Set up a new bot for me I can trigger when a charge is wrong. Walk me through connecting Gmail, then configure it: pull the receipt and the statement line, draft the dispute letter with the details laid out properly, and track the case number and deadlines once I've sent it. I review and send everything myself. Ask me for one wrong charge to work now, show me the letter, then save it.

Set up a new bot for me I can trigger for an unsubscribe sweep, in its own dedicated chat. Walk me through connecting Gmail, then scan the messages I archived in the last 120 days, identify marketing emails, and unsubscribe me from each one. Show me the complete list of senders and the unsubscribe action before it touches anything, and hold every action for my approval. Ask me whether any sender or mailing list is sacred, do the first sweep with me watching, then save it.

Set up a new bot for me I can trigger for discussions, explanations, and project guidance about open-source AI and computer science, in its own dedicated chat. Walk me through connecting GitHub and arXiv, then configure it: explain computer science concepts at my level, discuss open-source AI tools and projects with their licenses and tradeoffs, point me to relevant papers and repositories, and help me plan or review small learning projects without presenting uncertain information as fact. Ask me about my background, preferred programming languages, interests, and whether I want theory, implementation, or open-source project guidance, do a supervised first discussion with me, then save it.

Set up a new bot for me on a weekly schedule. Walk me through connecting Salesforce and Notion, then configure it: score every account on fit times warmth, write the tiers into a Notion database, and enrich contacts for the top tier in batches so the list is workable, not just ranked. Ask me what fit and warmth mean for our product, let me sanity-check tier one before the first full run, then save it.

Set up a new bot for me that turns a track into a music video. Walk me through connecting AITuber at https://mcp.aituber.app (https://aituber.app) and linking the channel it posts to. Then configure it: either write and generate the song from my brief, style and lyrics, or use a track I upload; once the song is ready, build the video from it as a new AI image every few seconds, as short AI clips, or as one cover still held for the whole song, in the art direction and image style I set. Quote the song and the video separately before either one runs. Then publish it with a title, description and tags. Ask me about the genre and mood, whether it is instrumental, whose words it sings, the visual direction, and the aspect ratio. Play me the song before it makes any visuals and show me the finished video before it posts, then save it.

Set up a new bot for me that runs automatically after each of my calls. Walk me through connecting Gong, then configure it: leave timestamped comments where I talked over someone, missed a buying signal or skipped discovery, and end with two things to practise before the next call. Ask me which methodology we run, coach one past call so I can read it end to end, then save it.

Set up a new bot for me that checks every 6 hours. Walk me through connecting Slack, then configure it: watch the competitor pricing pages I list, and when something changes send me a diff of old and new plus one line on what it probably means. Ask me which pages to watch, which channel to post in and how sensitive the diff should be, then save it.

Set up a new bot for me I can trigger to discuss ideas and brain-storming in the style of Elon Musk, in its own dedicated chat. Walk me through connecting X, then configure it to read Elon Musk’s public X feed once a day, summarize new themes and arguments, and use the accumulated summaries as context when I ask for analysis or share an idea; clearly label speculation and never present generated text as Elon Musk’s actual words. Ask me which parts of the feed matter most, how much historical context to retain, and what tone or level of challenge I want, run a supervised first feed review with me, then save it for a daily update.

Set up a new bot for me I can trigger to complete hands-on development tasks such as clicking a deployment or capturing a screenshot, in its own dedicated chat. Walk me through connecting the environments and services I use, then configure it: inspect the requested task, carry out the required interactive action rather than merely describing it, return evidence such as the deployment result or screenshot, and report any blockers. Ask me which environments are safe to use, which deployment targets require extra caution, and what evidence counts as done, do the first task with me watching, show me the exact action and target and get my approval before any deployment or other consequential action, then save it.

Set up a new bot for me in its own dedicated chat that acts as a lightweight CFO for my SaaS business. Walk me through connecting Stripe, Xero or QuickBooks, and Gmail, then schedule a weekly scan of spending to flag missed charges or unusual items, perform a cost-of-goods-sold audit, and produce a monthly CFO report with revenue, costs, notable changes, and questions requiring attention. Ask me about my accounting system, COGS definitions, reporting periods, budgets, vendors, and materiality thresholds, run the first scan and audit with me watching, and require my approval before it changes records, pays anything, or contacts anyone; then save it for weekly scans and a monthly report.

Set up a new bot for me, in its own dedicated chat, that manages my social media through OmniSocials. Connect to the hosted OmniSocials MCP server at https://mcp.omnisocials.com using my API key from Settings > API in the OmniSocials app (or install @omnisocials/mcp-server locally if this agent doesn't support remote MCP). Once connected, list my connected accounts and confirm which channels — Instagram, Facebook, LinkedIn, YouTube, TikTok, X, Pinterest, Bluesky, Threads, Mastodon, or Google Business — I want this bot to manage, and which workspace to use if I have more than one. Ask me my brand voice, content pillars, hashtag sets to reuse, posting cadence, and which platforms need distinct copy versus a shared caption. Ask for my approval boundaries: whether every post and reply needs my review, or only first-time content types. Before drafting anything, pull my account and post-level analytics — impressions, engagement, and follower change per platform — and flag which recent topics and formats performed best and worst. Check each connected account's best-times-to-post data and use it to propose schedule times instead of a fixed cadence, and check my current calendar so nothing clashes with what's already scheduled. Draft a batch of platform-specific posts from the topics and media I give it, favoring what the analytics showed works, and using per-platform media and alt text where the platform supports it. Show me the full batch — captions, target channels, and schedule times — before publishing or scheduling anything, and only publish what I explicitly approve. Separately, check my inbox across connected accounts for new comments and messages. For each unread conversation, summarize what's being asked and draft a suggested reply in my brand voice; send only the replies I approve, then mark the conversation read. Flag anything that needs a human tone I shouldn't auto-draft, like complaints or refund requests. Save this as a recurring bot once the first posting batch and inbox pass both go out clean — publishing on the cadence I approve, and checking the inbox daily.

Set up an always on teammate that reads the new videos from the channels I follow so I do not have to watch them. Walk me through connecting TranscriptAPI (transcriptapi.com), which returns YouTube transcripts and video and channel search. Ask me which channels to follow, the topics I care about most, how long a summary I want, whether to skip anything under a length I set, and my timezone and digest time. Also ask me where to deliver the digest, and connect only what I pick: right here in this chat by default, or Slack, email, Discord or Telegram. Run every morning at my time: find the new uploads on my channels since the last run, pull each transcript, and for every video give me the title, the channel, a summary in the length I chose, the three to five key points, any resource or tool mentioned, and the one line worth clicking in for. Keep a state file of every video already summarized so nothing repeats. Send me one digest wherever I chose to receive it, most relevant first, leaving out channels that posted nothing. If nothing new dropped anywhere, a single line. Never post or share any of this. Run one dry run over yesterday's uploads to set the summary length and ordering, then save it. TranscriptAPI is an independent service and is not affiliated with YouTube or Google.

Set up a new bot for me that watches appointment calendars. Walk me through connecting Slack, then configure it: check the passport, visa or DMV booking page for openings at my locations, and when a slot appears in my date range, ping me and book it after I confirm in the thread. Ask me which offices, which service, my date range, and the details the form needs, walk one dry run together, then save it.

Set up a new bot for me I can trigger when I receive contractor quotes. Walk me through connecting Gmail, the relevant contractor websites, and Google Sheets, then configure it: collect quotes and scope details, compare prices, timelines, exclusions, and warranties, identify negotiation opportunities, and draft or send focused counteroffers to contractors based on my instructions. Ask me about my target budget, must-have scope, preferred timeline, walk-away limits, negotiation tone, and which terms are sacred, show me each proposed message and the expected outcome before sending anything, do the first negotiation with me watching, then save it.

Set up a new bot for me called Design Engineer that I can trigger whenever I need to turn an idea, brief, screenshot, sketch, existing design, or product feedback into a real editable artifact. Walk me through installing and connecting the MagicPath plugin first. Ask for the goal, audience, platform, product context, brand or design system, constraints, source material, and desired fidelity. Use MagicPath as the working canvas—not as an image generator—to create and iteratively edit live, interactive, deployable interfaces, reusable components, complete pages and apps, wireframes, user flows, flowcharts, diagrams, and graphs. Keep related artifacts together on the canvas, explore multiple directions when useful, explain important tradeoffs briefly, and preserve my ability to visually inspect and edit everything. If I provide a GitHub repository or ask to work from existing code, connect GitHub only with my approval, bring the relevant repository context into the MagicPath canvas, and preserve its design tokens, components, and conventions. Never push, merge, or open a pull request without asking first. Start with one dry run, refine it from my feedback, then save this as an on-demand bot I can trigger with a new design brief.

Set up a new bot for me called Getting Things Done. Walk me through connecting Gmail, Slack, Granola, and Google Calendar, then configure it: capture from those inboxes without creating tasks, clarify one item at a time into a next action, and when I ask, give me at most three next actions in this chat with one marked MIT. Calendar only gets appointments and deadlines. Nothing is created, sent, or changed unless I approve the exact visible action. Run a weekly review in this chat. Show me a first clarify pass with me watching, then save it.

Set up a new bot for me I can trigger for parallel development work. Walk me through connecting Linear, GitHub, and Cursor Background Agents, then configure it to fetch my selected Linear tickets, clarify any missing context with me, send independent tasks to agents in separate branches or worktrees, run tests and review the resulting changes, and open a pull request for each completed task while a QA agent starts testing as soon as a preview branch is available. Ask me which Linear teams and statuses to use, how to name branches, what testing and review standards apply, and how to handle overlapping acceptance criteria or edits to the same file. Show me the proposed task assignments and the first-run results before creating pull requests or sending any external updates, then save it for on-demand use.

Set up a new bot for me that sends a weekday digest. Walk me through connecting my LinkedIn session and Sales Navigator, then configure it: watch for compelling events from engineering, product and AI leaders and draft ready-to-send notes in my voice. Ask me which signals are worth a note, keep every note behind my approval for the first week, then save it.

Set up a new bot for me I can trigger when I want to order pizza. Walk me through connecting Pizza Hut and Papa John's, then configure it: ask what kind of pizza, toppings, size, crust, dietary needs, delivery or pickup preference, address, budget, and desired timing; show me friendly recommendations and the complete order with fees before placing it. Hold every order for my explicit approval, then place it with the restaurant I choose. Ask me about my usual preferences and any ingredients to avoid, do a supervised first order with me watching, then save it.

Set up a new bot for me I can trigger by sending a recipe photo. Walk me through connecting my photo library and Whole Foods delivery, then configure it: read the recipe, identify ingredients and quantities, resolve reasonable package sizes and substitutions, turn the result into a Whole Foods delivery cart, and group ambiguous items for my review. Ask me about dietary restrictions, preferred brands, pantry staples I already have, acceptable substitutions, delivery location, and budget, show me the full cart with quantities and total, and hold the order for my approval before placing it. Do a supervised cart-building trial with one recipe, then save it.

Set up a new bot for me in its own dedicated chat that keeps my SaaS marketing work consistent. Walk me through connecting Slack, GitHub, and my CMS, then schedule a weekly review that checks the user-facing features we shipped, identifies the most useful updates, and prepares the marketing actions and copy I should consider. Ask me which channels, audiences, product areas, brand guidelines, and publishing workflows matter, do the first review with me watching, and show me everything before it sends or publishes anything; then save it for a weekly run.

Set up a new bot for me for school and camp paperwork. Walk me through connecting Google Drive and Gmail, then configure it: when a new form lands, fill it from last year's PDFs — same kids, same doctors, same emergency contacts — and ping me only for the parts that changed and the signature. Nothing is submitted without me. Ask me where last year's forms live, fill one current form for me to check, then save it.

Set up a new bot for me, in its own dedicated chat, that operates my social publishing through Delulu Social. Before configuring it, check whether the `manage-social-publishing` skill is available; if not, install it with `npx skills add thegesturs/delulu --skill manage-social-publishing --global --yes`, tell me to start a fresh chat if the current agent cannot load newly installed skills, and continue from this exact prompt. Read the current agent setup guide at https://docs.delulu.social/getting-started/agent-setup/, MCP overview at https://docs.delulu.social/mcp/overview/, MCP tool reference at https://docs.delulu.social/mcp/tools/, publishing guide at https://docs.delulu.social/guides/publishing/, and agent discovery manifest at https://solulu.delulu.social/auth.md so the workflow follows current Delulu behavior rather than guessed commands. Prefer the hosted MCP server at `https://solulu.delulu.social/mcp` when the agent supports remote MCP and browser OAuth; otherwise use the Delulu CLI through the skill. Never ask me to paste access or refresh tokens. Walk me through authorizing the correct workspace, inspecting setup status, listing existing social accounts before connecting duplicates, completing any required provider consent, and connecting the Google Drive folder where approved source material lives. Then ask which accounts, timezone, cadence, brand voice examples, content pillars, links, exclusions, media rules, and approver to use. Before each run, read the live workspace role, connected accounts, usage, pending reviews, existing failures, and scheduled posts. Each week, use only approved source material to create channel-specific copy and a proposed seven-day calendar; preserve attribution and links, never invent claims or media rights, and never paste identical copy across networks. Default every new item to an unscheduled draft. Show me the final copy, target accounts, media, privacy, and resolved local schedule before any external action, and schedule or publish only the items I explicitly approve. Use public HTTPS media with MCP only after I approve sharing it; use the CLI for local files. Treat returned post and target states as authoritative: report `pending_review` instead of bypassing it, keep the original post and operation identity while publishing is in progress, and retry only failed targets so successful destinations are never duplicated. Run the first batch from one real approved source as drafts with me watching, incorporate my edits into the operating rules, then save the bot on the agreed weekly schedule.

Set up a new bot for me I can trigger when I give you a task that needs background work. Walk me through connecting Google Calendar, Slack, and Email, then configure it: track the task through its current step, check whether the work is still progressing, and send me a status update every 10 minutes until it is complete, blocked, or needs my input; if a scheduled check-in fails, retry it and tell me rather than going quiet. Ask me how often to check in, which channel to use, what counts as blocked or complete, and which tasks should be excluded. Show me a dry run with a sample task, draft the first notification for my approval before sending it, then save it.

Set up a new bot for me that runs daily at 8:00am. Walk me through connecting Apple Search Ads and Slack, then configure it: post spend against plan, what's over-delivering and what to cut, and when I reply in the thread make the bid edit and confirm what changed. Ask me for the daily plan and guardrails, require confirmation above my threshold, then save it.

Set up a new bot for me in its own dedicated chat that operates my affiliate program as a practical affiliate manager. First, ask for my business goal, reporting timezone, currencies, success metrics, approval rules, partner communication channel, and weekly meeting cadence. If my agent host supports Agent Skills, load the Affonso affiliate-manager skills from `affonso-io/agent-skills`: affiliate-performance-manager, affiliate-partner-qualification, affiliate-partner-activation, affiliate-fraud-review, affiliate-campaign-manager, affiliate-compliance-monitor, and affiliate-profitability-manager. If terminal access is available, install the Affonso CLI with `npm install -g @affonso/cli`; ask me to set my own `AFFONSO_API_KEY` securely in the environment, never in chat or logs, and verify access with `affonso whoami --json`. If skills, terminal access, or authentication are unavailable, state exactly what is missing and do not invent data. Every Monday morning in my timezone, run a read-only operating review. Use `--json` on every Affonso CLI command and page through the entire relevant result set. Compare the last 30 days with the preceding 30, unless I choose another period. Read the program configuration, restrictions, payment terms, fraud rules, affiliates, referrals, commissions, payouts, active campaigns, coupons, and creatives as needed. Return a short executive brief with three to five material changes, then separate prioritized actions into `grow`, `retain`, `fix`, and `investigate`. Include a compact partner table with current output, trend, evidence, opportunity or risk, recommended action, owner, and check-in date. Flag concentration risk, dormant high-potential partners, pending commission or payout exposure, new applications needing review, suspicious referral patterns, and policy or disclosure risks. Clearly distinguish observed facts, hypotheses, and unavailable data. Calculate conversion rate, EPC, margin, LTV, CAC, payback, or ROI only when their valid inputs are available; never fabricate financial assumptions. For each recommended action, prepare the smallest useful next step: an applicant decision with rationale, a partner activation plan and draft, a fraud or compliance evidence table, or a campaign brief with eligible partners, measurement plan, and proposed assets. Never approve or reject an affiliate, alter groups, commissions, payment terms, restrictions, fraud rules, coupons, creatives, or program settings; never process, hold, cancel, or complete a payout; and never contact a partner. Instead, show the exact affected IDs, proposed change, evidence, expected impact, and downside, then wait for my explicit approval. Treat fraud signals as review evidence, not a verdict, and escalate legal or policy interpretation questions to me. Run the first review with me watching and ask me to approve the briefing format and any proposed follow-up actions before scheduling it. On future runs, report only material movement since the previous review, track the status of actions I approved, and surface the one decision that deserves my attention this week. Save the bot only after I approve the first review.

Set up a new bot for me. Walk me through connecting the Airtable applications table and Gmail, then configure it to run when I trigger it: read every application, score fit against our ICP with a one-line reason, and batch the clear fits for approval. Ask me to write out the ICP, show me the first batch for correction, then save it.

Set up a new bot for me that runs daily to fetch the latest data from the BotDirectory API. Walk me through connecting the API and configuring authentication, then schedule a daily request, retrieve the available directory data, and show me a clear summary of what was fetched with any errors or missing fields. Ask me what time zone and delivery destination I want and whether I want the raw response, a summary, or both, do the first fetch with me watching, then save it for a daily run.

Set up a new bot for me I can trigger for a purchase-benefits audit, in its own dedicated chat. Walk me through connecting Gmail, then scan purchase receipts, gift-card emails, and order confirmations to find unused gift cards and purchases whose return windows have expired, and give me a clearly sourced report with merchant, amount or item, purchase date, gift-card balance when available, and return-window status. Ask me which stores and accounts to include, whether digital and physical gift cards both matter, and how far back to search, do the first audit with me watching, then save it for a monthly run.

Set up an always on teammate that keeps me on top of everything moving in my domain on YouTube, so I hear about a launch, a tool or a shift in the conversation before my competitors do. Walk me through connecting TranscriptAPI (transcriptapi.com), which returns YouTube transcripts and video and channel search. Ask me the domain I work in, the search terms and topics that define it, the channels, conferences, analysts and podcasts that cover it, the kinds of things I care about (launches, funding, pricing moves, integrations, opinions and predictions, user complaints and wishes), and how far back to reach on the first run. Also ask me where to deliver the digest (this chat, Slack, email, Discord or Telegram) and where to keep the running record (a Notion database, a Google Sheet, or just a state file), and connect only what I pick. Run every weekday: search my terms across YouTube and check the channels I named for new uploads, pull each new transcript, and pull out what is genuinely new: products launched or announced, pricing and packaging moves, notable opinions or predictions, and any recurring user pain or request. Keep a state file of every video id processed so nothing repeats. Send me one digest wherever I chose, at most eight items, each in one line with a short quote in their words and the timestamp, the video title and channel, and one line on why it matters. Append everything to my chosen record with the date so the picture builds over time. Once a week add a trend line. If nothing new, a single line. Quote sparingly and always link the source and timestamp. Never republish a transcript and never post any of this publicly. Run one dry run over the last two weeks of my terms, then save it. TranscriptAPI is an independent service and is not affiliated with YouTube or Google.

Set up a new bot for me that monitors customer journeys on my website and turns confirmed friction points or errors into draft pull requests. Walk me through connecting PostHog, Fable, and GitHub, then configure it to review journey recordings and event data on a schedule or webhook, identify reproducible usability problems and errors, gather the relevant context, and create a clearly described pull request for me to review. Ask me which journeys, events, error thresholds, repositories, and coding conventions matter, do a supervised dry run that produces a sample finding without changing production, require my approval before creating or publishing any code, then save it.

Set up a new bot for me as a daily routine before my first meeting. Walk me through connecting Google Calendar, Salesforce, Gmail, Slack, Granola and Gong, then configure it: for every meeting on my calendar today, pull what we know from the CRM, recent email, Slack threads and past call notes — or do online research if it's a new account — and give me one short, skimmable brief I can read on my phone while commuting. If I have a slides bot, let it ask that bot for a customized deck ahead of the calls that need one. Ask me what time to send it and what a good brief looks like to me, run it for tomorrow's meetings, then save it.

Set up a new bot for me. Walk me through connecting Gmail and LinkedIn, let it learn how I write from my sent mail, then schedule it daily: research each person, draft outbound in my voice, send from my account, and report what went out and why. Hold the first ten for my approval, then save it as a running bot.

Set up a new bot for me that covers a Slack channel as my assistant. Walk me through connecting Slack, then let it learn my voice and my usual answers from the channel history: handle the routine questions the way I would, and bring me anything new, sensitive, or where it's guessing — with a drafted reply ready to approve. Ask me which channel, what's always mine to answer, and how it should sign off, run it in draft-only mode for the first week, then save it.

Set up a new bot for me so I can stop opening social apps. Walk me through signing in to Instagram, LinkedIn, and X myself in your persistent browser. Never ask for, type, or store my passwords; hand me the browser for login, 2FA, or payment steps. Then operate read-only on a schedule: - LinkedIn around 7:00 a.m.: surface important unread DMs, tags and replies, real connection requests or inbound opportunities, and meaningful network updates such as job changes, launches, funding, or major news. Skip generic recommendations, ads, and engagement noise. - X around 7:15 a.m.: summarize the last 12 hours of my home timeline and any genuinely big news. Prefer the signed-in browser session when API access is unavailable or limited. - Instagram around 7:30 a.m.: find significant life events from friends and mutuals (engagements, weddings, babies, deaths, and similarly important updates), urgent notifications, and unread DMs. Skip ads, suggested posts, brand content, and filler. Each run should send one concise digest. If nothing matters, say nothing. Never like, post, follow, connect, comment, reply, or send a message unless I explicitly ask in that moment. Ask me which people and topics should always count as important, let me change the schedules and filters, then save these instructions as the bot's standing behavior.

Set up a new bot for me I can trigger with a destination and dates. Walk me through connecting Gmail and Google Slides, then configure it: find Airbnbs that fit our budget and taste, build a short deck — photos, prices, distances, pros and cons — and email it to my partner for the final vote. Ask me for budget, vibe and dealbreakers, build one deck for a trip we're actually planning, then save it.

Set up a new bot for me that drafts on weekdays. Walk me through connecting X, LinkedIn and Notion, let it learn my voice from my past posts, then configure it to draft the next ones into Notion for review, matching my rhythm and not just my topics. Nothing publishes without me. Ask me for twenty posts I'm happy with, then save it.

Set up a new bot for me on a weekly schedule. Walk me through connecting our ad platform and Notion, then configure it: scan ad performance, explain in plain language why the winners are working, and write the next tests it would run — hypothesis, audience, creative angle — into a Notion backlog I review. Ask me which campaigns matter and what a meaningful difference looks like, draft the first backlog for me to edit, then save it.

Set up a new bot for me I can trigger for a daily fetch. Walk me through connecting the BotDirectory API, then configure it to fetch the directory data once each day, save the latest results, and show me what is new or changed since the previous fetch. Ask me what time and timezone to use and where I want the results reported, do the first fetch with me watching, then save it for a daily run.

Set up a new bot for me that watches for campsite openings. Walk me through connecting Slack, then configure it: check recreation.gov and ReserveCalifornia for the sites and dates I care about, and when something opens, message me the details and book it only after I confirm in the thread. Ask me for my parks, date windows, and site preferences, do a dry run on a weekend I don't want so I can see the flow, then save it.

Set up a new bot for me that turns a rough bug report or feature idea into a clean GitHub issue. Walk me through connecting GitHub, then configure it: when I describe a problem or idea, ask me one clarifying question at a time — what happened, what I expected instead, when it started, how often it occurs — until you have enough to write it up, and stop as soon as you do. If I give you repo access, look through the relevant code first for existing terminology, tests, and related issues so the write-up uses the project's own language instead of my rough paraphrase. For bug reports, try to trace and reproduce the issue and say plainly if you couldn't rather than guessing. Classify it as a bug or an enhancement, then draft the full issue — summary, current vs. expected behavior, repro steps, acceptance criteria — without file paths, line numbers, or commit SHAs since those go stale within days. Show me the draft, ask if anything's missing or overstated, and only publish once I approve it; if you can't publish directly, hand me the finished markdown to paste in myself. Ask me which repositories you're allowed to file into and whether you need my sign-off on labels before publishing, do a dry run on a real bug I describe to you, then save it.

Set up a new bot for me I can ask technical product questions live on customer calls. Walk me through connecting our codebase on GitHub — or Glean, if I don't have repo access — then configure it: when a customer asks something deeper than my product knowledge, answer from the source of truth and hand me a customer-facing answer I can say out loud, without me pinging an engineer or digging through Slack, Notion and docs. Ask me which repos or knowledge sources count and how technical my customers are, test it on three questions from my last call, then save it.

Set up a new bot for me that plans software work and delegates implementation to command-line coding agents on a remote machine. Walk me through connecting the remote VM, Codex CLI, and Claude Code, then configure it so I can give you a repository, issue, or large context dump; you perform the high-level planning pass, send the relevant context and implementation tasks to Codex or Claude Code in isolated worktrees, collect their results, reconcile conflicts, and return a tested summary with diffs and next steps. Ask me which CLI should handle planning versus implementation, how the machines authenticate, which repositories and branches are allowed, what commands and tests are safe to run, and how much autonomy the agents have. Do a supervised dry run on a small task, show me plans and diffs before merging or opening pull requests, then save it for on-demand use.

Set up a new bot for me I can trigger whenever a questionnaire lands. Walk me through connecting Google Drive and Notion, then configure it: draft answers from our public docs and past responses, cite what it can, and flag every question that genuinely needs a human. Ask me where past questionnaires live, run it once on a real one, then save it.

Set up a new bot for me I can trigger for customer support from my phone or laptop, in its own dedicated chat. Walk me through connecting Claude and my support conversations, knowledge hub, and relevant product context, then configure it: review incoming support requests, distinguish real customer issues from spam, answer routine questions from the knowledge hub, triage feature requests and bugs, document the context and recommended resolution, and prepare fixes or other resolutions for my review. Keep an audit trail linking each request to its classification, response, documentation, and proposed fix. Show me the full triage and every drafted customer reply, code change, or production action before sending or deploying anything, and wait for my explicit approval. Ask me which issues are urgent, what resolutions you can handle, which changes are sacred, and how I want feature requests prioritized, run the first support batch with me watching, then save it for on-demand use.

Set up a new bot for me in its own dedicated chat that gives me a daily digest of what my Grok bot swarm accomplished. Walk me through connecting the bots and their conversation histories, then configure it to review the previous day's activity, group work by project and bot, summarize completed tasks, decisions, open questions, failures, and next steps, and link each conclusion to the relevant bot conversation when possible. Ask me what projects, outcomes, and channels matter most and what level of detail I want, run the first digest with me watching, then save it for a daily run.

Set up an always on teammate that tells me what my house is actually worth this month, and which sale nearby moved the number. Walk me through connecting Zillapi (zillapi.com), which returns Zillow property data for any US address. Ask me my address, what I paid and when, my mortgage balance, rate and payment if I want the equity and refinance lines, and the radius that counts as my street. Also ask me where to send the monthly update, and connect only what I pick: this chat, Slack, email, Discord or Telegram. Run on the first of each month: pull my property record, Zestimate and rent Zestimate, tax history, and the comparable homes nearby that recently sold, went under contract or changed price. Keep a state file of every reading so each update is a change, not a restatement. Send me one update wherever I chose, short enough to read on a phone: my Zestimate and how it moved since last month and since I bought, my estimated equity, the single nearby sale or price change that best explains the move, my rent Zestimate and what the house would earn rented, and where my assessed value sits against the estimated value. If it barely moved, a single line. Raise a flag only when actionable: assessed value climbing faster than nearby estimates (property tax appeal worth a look), equity crossing a threshold I set, or the rent Zestimate moving enough to change the rent versus sell question. Report neighbours only as aggregate comparisons and the specific sales that explain my number, never a profile. Run one dry run, then save it. Zillapi is an independent service and is not affiliated with Zillow Group, Inc.

Set up a new bot for me I can trigger for studying how to study. Walk me through pointing it at a local folder of learning-science books and notes, keep every original PDF and EPUB read-only, then configure it: turn that folder into a 7-day practice lab built on Make It Stick — retrieval, spacing, and interleaving — with a local offline kit for today's drill, recall cards, a review calendar, mixed problem types, a weakness log, and a four-box reading map. Ask me which folder to use, whether the learner is a student or an adult, which subjects to practice, and which day to start, run Day 1 with me (hide the text, write two sentences from memory, schedule the next review question), then save it.

Set up a new bot for me I can trigger for weekday plumbing-content planning and review, in its own dedicated chat. Walk me through connecting Webflow and my existing content planner, then configure it: compare how my Phoenix plumbing company currently appears online with how I want to be perceived, choose useful local search topics and keywords, maintain a planner with the date, keyword, title, draft, review notes, and live URL, and review each draft for factual accuracy, useful pricing transparency, SEO issues, and HTML or formatting mistakes before it is queued for publication. Show me the complete draft and your proposed edits before anything is published. Ask me about my service area, ideal customers, services and pricing claims, topics to avoid, brand voice, and which facts are sacred, run the first article plan and review with me watching, then save it for each weekday.

Set up a new bot for me I can hand two PDFs. Walk me through connecting Google Drive, then configure it: compare the old and new lease, policy or contract, and give me a one-pager of what actually changed — money, dates, obligations, anything quietly added or removed — with page references so I can verify. Ask me nothing it can read for itself. Run it on a pair I've already read closely so I can check it catches everything, then save it.

Set up a new bot for me that gets conversion tracking working on my website using Converly. Walk me through connecting Converly (a new account comes with a free trial), then ask me which website, which form tool the site uses, and which ad platforms should get the conversions, like Google Ads, Meta, GA4, LinkedIn or TikTok. Build the conversion flow in Converly, hand me the authorization link when an ad platform needs my login, give me the tracking snippet with instructions for my site builder, then publish the flow and verify it with a test conversion. Never ask me to paste ad platform passwords into chat, and report exactly what was verified and what still needs a real form submission to prove. Then save it so I can run it again for another site or ad platform.

Set up a new bot for me that stays always on so I can ask CRM questions from my phone. Walk me through connecting Salesforce read-only and Slack, then configure it: when I ask about the quarter, give me the number, the three deals that move it, and where the data looks wrong. Ask me for quota and quarter definitions once, let me test three questions I know the answers to, then save it.

Set up a new bot for me that triggers on my sales calls. Walk me through connecting Granola and Google Slides, then configure it: watch notes as they come in, copy the master deck and rewrite the slides to match what this customer cares about, and have the new deck ready before my next call. Ask me for the master deck, test it on one recorded call, then save it.

Set up a new bot for me I can trigger when a customer asks for enablement material. Walk me through connecting Gmail, Zoom and Google Drive, then configure it end to end: find the request email, pull the relevant call recordings, summarize them into a pack, drop everything into a Drive folder, and draft the reply with the link. I send the reply myself. Ask me for one past request to reproduce, let me compare its pack to what I sent manually, then save it.

Set up a weekly bot that finds strong evergreen posts worth reusing. Walk me through connecting FeedHive, Notion and Slack, then ask which accounts to analyze, what performance threshold to use and which topics must never be recycled. Each week, nominate up to five proven posts, exclude anything dated or no longer true, and create fresh channel-specific versions as unscheduled FeedHive drafts. Send them to me for approval and never publish automatically. After approved versions run, compare their performance with the originals. Run the first analysis read-only, then save it.

Set up a new bot for me I can trigger to prepare external email drafts, in its own dedicated chat. Walk me through connecting Gmail, then configure it: turn my instructions and relevant email context into clear, appropriately toned drafts, apply a dedicated draft label, and never send anything automatically. Ask me which recipients and message types need special handling, what tone and sign-off to use, and which messages are sacred, do a supervised first draft with me watching, show me every draft for approval before it is sent, then save it.

Set up a new bot for me I can trigger for recurring finance administration, in its own dedicated chat. Walk me through connecting my self-hosted finance system, then configure it: review financial records and pending changes, maintain a finance task list, identify discrepancies or items needing attention, and prepare proposed updates without writing anything back until I approve them. Ask me which accounts and categories to include, what thresholds or transactions need special review, and who can approve changes, do the first review with me watching, show me the full proposed write set and require explicit approval before making any change, then save it for a recurring run.

Set up a new bot for me on a daily schedule. Walk me through connecting the global webinars Notion database and my calendar, then configure it: keep my local marketing calendar in sync — new events appear, cancelled ones disappear, changes propagate — without me copying entries by hand. Ask me which regions and event types are mine, run one sync while I compare both calendars, then save it.

Set up a new bot for me that watches the weather at my airports. Walk me through pointing it at Aviation Weather Center METARs for the fields I fly between, then configure it: monitor the current and recent observations, and for the next three-hour window predict whether conditions are trending toward a no-go for my flight, showing me the historical and current snapshot it's basing that on. Make it clear this is a heads-up, not go criteria — I still make the call from the official brief. Ask me for my airports, my personal minimums and how often to check, run it for the next 24 hours so I can compare it to what actually happened, then save it.

Set up a new bot for me that preps my weekly manager sync. Walk me through connecting Granola and Google Calendar, then configure it: before each 1:1, pull the notes from our last one, list the tasks my manager and I discussed and where each stands, set reminders for the ones I owe, and give me a short agenda of what to raise this week. Ask me who my manager is and which recurring meeting is our 1:1, prep the next one so I can check it, then save it.

Set up a new bot for me on a weekly schedule to keep our account org charts current. Walk me through connecting Salesforce and my LinkedIn session, then configure it: a name or an email is enough to find the rest, place people in the chart, and mark who influences the deal versus who just attends. Ask me which ten accounts matter this quarter, show the first map for the AE to check, then save it.

Set up a new bot for me that builds prospecting sheets, ideally overnight so they're ready in the morning. Before the first run, ask me one round of setup questions — which CRM, email and spreadsheet I use, whether I have product usage data, an intent tool or call notes, whose accounts to pull by default, which titles and functions count as my buyers and what seniority mix I want, and any hard writing rules — then save the answers and reuse them. Learn my voice from 15 to 30 real sent prospecting emails, stripped of signatures and quoted threads, and keep a style profile of how I open, make the ask and sign off, refreshed every 30 days or so. On each run confirm the title filter, seniority mix and account and contact counts with me rather than assuming last time's, discover the CRM's real field and stage names first, pull accounts I own with no active mid-funnel opp, and select contacts strictly against the confirmed filter, deduped by person. Enrich every row with per-account compelling events — funding, launches, AI initiatives, exec hires — and per-contact recent posts or talks with citations, actually watching or transcribing a recent podcast for a grounded takeaway, and write "no verifiable recent posts found" rather than inventing anything; add usage and plan-limit hits and intent signals if I have them. Surface open opp stage, amount and last CRM activity on every row, and mark anyone I've emailed in the last 90 days as Skip Draft. Deliver a live spreadsheet link, never a CSV, then draft an email of a subject plus 3 or 4 sentences and a shorter LinkedIn note off the same hook for each contact not skipped — the LinkedIn note never mentions the email. Show me 2 or 3 pairs for approval before the full batch, drafts only, and after I send, reconcile the sheet against my sent mail so it never double-drafts. Run it once on a small batch with me watching, then save it.

Set up a new bot for me I can trigger when I need to understand or apply regulatory requirements, in its own dedicated chat. Walk me through connecting Google Drive, then configure it: read the regulations, policies, and internal procedures I provide, map requirements to the relevant business processes, explain them in plain language, identify gaps and conflicting obligations, and produce a cited compliance checklist with uncertainty clearly marked. Ask me which jurisdictions and industries apply, what kind of organization and data are involved, which sources are authoritative, and how often the materials change, run the first analysis on a small document set for my review, show me every recommended action before it is filed, communicated, or used to change operations, then save it for on-demand reviews.

Set up a new bot that turns product releases into social campaigns. Walk me through connecting GitHub, Postiz and Slack, then ask which releases count, which accounts to use and who approves drafts. When something ships, pull only verifiable customer-facing changes and create platform-specific drafts in Postiz rather than copying the same post everywhere. Send me the drafts and proposed schedule in Slack, and never publish without approval. After the posts have been live for 72 hours, send a short performance summary. Test it on one past release as drafts only, then save it.

Set up a new bot for me I can trigger on every pull request or dependency update. Walk me through connecting GitHub and GitHub Actions, then configure it: inspect dependency manifests, lockfiles, release changes, build workflows, and third-party packages for software supply-chain threats, correlate suspicious behavior with known advisories, explain the evidence and severity, and return prioritized remediation steps without changing code or blocking releases automatically. Ask me which repositories, languages, environments, advisories, and severity thresholds matter, do a supervised scan of one repository first, show me the findings and any proposed issue or workflow changes before publishing them, then save it.

Set up a new bot for me in its own dedicated chat that helps run customer support. Walk me through connecting my helpdesk software and support documentation, then configure it to pull new tickets every 30 minutes, use my docs to draft the best answers it can, and organize tickets that need human attention. Ask me which ticket types, escalation rules, tone, and sources of truth to use, show me a supervised dry run, and hold every response for my approval before sending it; then save it for continuous operation.

Set up a new bot for me that runs when a support ticket arrives, in its own dedicated chat. Walk me through connecting Ferndesk, GitHub, Axiom, Infisical, and my VPS, then configure it to keep each run bounded to the ticket conversation ID, read the relevant documentation, inspect the codebase and logs, analyze the customer's error, determine whether it is a bug, and prepare a code fix as a draft pull request plus a draft customer reply. Run it from webhooks with a cron fallback inside a sandbox with only the tools it needs, never expose secrets, and never send the reply or merge the pull request without my approval. Ask me which repositories, log sources, documentation areas, ticket labels, and approval rules to use, do a supervised dry run on a representative ticket, then save it.

Set up an always on teammate that tells me what my competitors said out loud this week, before any of it reaches their blog. Walk me through connecting TranscriptAPI (transcriptapi.com), which returns YouTube transcripts and video and channel search. Ask me the competitors and channels that cover my category (their channels, conference and analyst channels, podcasts on YouTube), the terms I care about (my and competitors' product names, category words, pricing and integration words), and how far back on the first run. Also ask me where to deliver the briefing (this chat, Slack, email, Discord or Telegram) and where to keep the record (a Notion database, a Google Sheet, or a state file), and connect only what I pick. Run every weekday: check each tracked channel for new uploads, and search my terms across YouTube to catch videos on channels I am not tracking yet. For every new video pull the transcript and read it for four things: what they are shipping or deprecating, statements about price, packaging or limits, the objections and comparisons they raise including about us, and any customer or number they cite as proof. Keep a state file of every video id processed. Send me one briefing wherever I chose, at most six items, each with the claim as a short quote in their words, the timestamp, the video title and channel, and one line on why it matters to us. Append every item to my chosen record with the date. If nothing new, a single line. Monthly rollup: who talked most, what changed in how they position against us, and any claim they quietly stopped making. Quote sparingly and always link source and timestamp. Never republish a transcript and never post any of this publicly, it is an internal briefing. Run one dry run over two weeks of one channel, then save it. TranscriptAPI is an independent service and is not affiliated with YouTube or Google.

Set up a new bot for me I can trigger when a product needs fresh creative. Walk me through connecting AITuber at https://mcp.aituber.app (https://aituber.app), then configure it: write ten short scripts for the product across the angles that sell it, and build a talking avatar video for each one. Pick the presenter from the avatar library or from a photo I upload, put the product in the shot as a prop so the pitch matches what people see, give the avatar a voice and speed or lip-sync it to audio I supply, and add the movement notes and captions that suit the platform. Hand the batch back numbered, with the script and the credit cost against each file. When I say which ones won, keep the angle, the presenter and the delivery that worked and write the next ten from those. Ask me about the product, the audience, the promise I am allowed to make, the claims legal will not sign off on, and whether the ads are portrait or landscape. Show me the scripts before it spends credits and the batch before I upload anything, then save it.

Set up an always on teammate that underwrites a short term rental purchase in the time it takes me to read the listing. Walk me through connecting Zillapi (zillapi.com), which returns Zillow property data for any US address, and StayingAPI (stayingapi.com), which returns availability and nightly price quotes for short term rentals. Ask me the markets I buy in, my target return and how I measure it, my assumptions for management, cleaning, utilities, insurance and maintenance, my down payment and rate, the occupancy I underwrite to, and whether I want this on demand, scheduled, or both. Also ask me where to deliver results (this chat, Slack, email, Discord or Telegram) and where to write the full model (a Google Sheet, a Notion database, or a state file), and connect only what I pick. On demand: I send an address or listing link; it pulls the property record, asking price, tax history and long term rent Zestimate, finds the eight to fifteen closest nightly comps by bedrooms, capacity and distance, pulls their nightly prices and booked nights over ninety days, and returns one page: estimated annual nightly revenue at the comp set's realized occupancy, the same at my underwriting occupancy, all in costs, net yield, the long term rent alternative, and the two assumptions the answer is most sensitive to. On a schedule: every weekday run new listings and price cuts through the same underwriting, with a state file. Send me one digest wherever I chose, only the properties that clear my target, at most five, each one line with address, asking price, modeled net yield, comp set occupancy, and the sensitivity note. Write the full model to my chosen record. If nothing cleared, a single line, and weekly tell me how close the best got. Say it out loud when the comp set is thin, when nightly prices look seasonal, or when local rules may restrict nightly renting, and never present the model as a valuation. Never contact an agent or make an offer. Run one dry run on a property I know well, then save it. Zillapi and StayingAPI are independent services and are not affiliated with Zillow Group, Inc., Airbnb, Booking.com, Vrbo or Google Hotels.

Set up a new bot for me to run community ops on a weekly schedule. Walk me through connecting Luma, Slack and the Notion member database, then configure it: sync events into the database, post the weekly summary, chase the follow-ups nobody remembers, and tell me what slipped. Ask me when the summary should go out, shadow one week without posting, then save it live.

Set up a new bot for me I can trigger for content requests from a specific person. Walk me through connecting Gmail, Claude, and Google Docs, then configure it: find the latest email from my chosen sender, extract the content brief, use the existing Claude project I name to create the requested content in its established context and voice, put the finished content into a Google Doc, and prepare a reply with the document link. Ask me which sender to monitor, which Claude project to use, how the Google Doc should be titled and shared, and what instructions or quality standards to follow; show me the first result and draft reply for approval before creating or sending anything, then save it for future requests.

Set up a new bot for me I can trigger for deal momentum. Walk me through connecting my CRM, Gmail, and Google Calendar, then configure it: review every open deal, identify stalled steps, missing information, decision-makers, risks, and the next action needed, then prepare follow-up emails, meeting requests, internal handoffs, and updated close plans to move each deal forward. Ask me about my sales stages, qualification rules, follow-up cadence, approval limits, and what makes a deal high priority, do the first pipeline review with me watching, show me every proposed message and calendar action before it is sent or booked, then save it for a daily run.

Set up a new bot for me I can trigger before a call. Walk me through connecting Google Slides, then configure it: keep the layout intact, translate the copy naturally rather than literally, and leave product names alone. Ask me which languages we sell in, produce one sample for a native speaker to read, then save it.

Set up a new bot for me that runs after each recorded demo. Walk me through connecting Zoom and Google Drive, then configure it: cut the recording into clips tagged by feature and question, file them in a library, and keep an index page so I can pull the right moment before the next demo instead of scrubbing an hour of video. Ask me for the tags that matter, process one past demo so I can check the cuts, then save it.

Set up a new bot for me that answers customer questions from our current documentation and reduces avoidable support tickets. Walk me through connecting Ferndesk and its documentation, then configure it to retrieve the most relevant up-to-date articles, answer customer questions with links or citations, identify when the documentation is missing or stale, and route uncertain questions to a support ticket instead of guessing. Ask me which documentation sources are authoritative, what topics are sensitive, how to handle unanswered questions, and what tone to use, review a supervised set of draft answers with me before enabling customer-facing replies, require approval for any response outside the approved confidence rules, then save it.

Set up a new bot for me I can point at a messy Drive folder. Walk me through connecting Google Drive and Notion, then configure it: rebuild the folder as a wiki — group by topic, name an owner per page, banner anything stale, and leave the originals untouched. Ask me for the folder and who owns what, do one subfolder first so I can check the structure, then save it to run on the rest.

Set up a new bot for me I can trigger with a feature name. Walk me through connecting Slack, then configure it: search every channel for who asked about that feature, from which customer, and in what words, and give me one list with links to the original messages — seconds instead of an hour of scrolling. Ask me which channels count and which are noise, run it once on a feature I already know the history of, then save it.

Set up a new bot for me I can trigger on a folder of film scans. Walk me through connecting my scanned-image folder and ExifTool, then configure it: inspect hundreds of scans, identify or collect the correct capture dates and GPS coordinates, fix the date and GPS metadata without altering the image pixels, preserve the original files, and produce a report of changed, uncertain, and skipped files. Ask me which date and coordinate formats to use, how to handle missing or conflicting information, what naming and backup rules I want, and whether uncertain edits require review, do a dry run on a small sample for my approval, then save it.

Set up a new bot for me in its own dedicated chat that grades the final solutions produced by my Grok bot chain. Walk me through connecting the upstream bots and their final outputs, then configure it to evaluate each solution against the criteria I provide, check completeness, accuracy, consistency, and required formatting, explain any failed criteria, and send the work back for revision when it does not pass rather than approving it automatically. Ask me to define the grading rubric, minimum passing score, retry limit, and escalation rules, run the first grading cycle with me watching, then save it as the final gate for future outputs.

Set up a new bot for me on a weekly schedule. Walk me through connecting Google Calendar, then configure it: find me at least 90 minutes of real focus time each week, propose the junk meetings to decline with a polite note drafted for each, and hold the block on my calendar. Declines only go out after my approval. Ask me what counts as junk and what's untouchable, show me the first week's plan, then save it.

Set up a new bot for me I can trigger to write Harry Potter fan fiction, in its own dedicated chat. Walk me through connecting Google Docs, then configure it: ask for the characters, era, premise, point of view, tone, length, and canon boundaries I want, draft an original story in that setting without copying published text, and save the draft to Google Docs. Ask me which themes and characters are off-limits, do a supervised first story with me, then save it.

Set up a new bot for me as a recurring routine. Walk me through connecting Gmail, let it learn how I write from my sent mail, then configure it: scan my work inbox for messages since the last run that plausibly need a reply — customer and prospect threads, renewal or pricing questions, intros, direct questions to me — and skip newsletters, automated notifications, receipts, calendar RSVPs and internal noise. For each one give me a short digest in chat: sender, subject, one line on what they need, and a proposed reply in my voice. Never auto-send. If nothing needs a reply, send no message at all. Ask me how often to run and who always counts as important, do one pass so I can check the drafts, then save it.

Set up a new bot for me that runs every morning. Walk me through connecting Gong and the Notion FAQ page, then configure it: add the new questions people asked on calls, merge duplicates, and flag answers that contradict what we shipped. Ask me to seed it with the questions we already answer daily, let me watch the merge behaviour for a week, then save it.

Set up a new bot for me that investigates failed email deliveries and prepares the next action for a technician or customer. Walk me through connecting MailOps, my SPF, DKIM, and DMARC records, and SMTP delivery context, then configure it to read each failure, correlate the authentication and SMTP details, identify the likely cause, and draft precise remediation instructions or a customer response. Ask me about my sending domains, escalation rules, technician workflow, and preferred response style, do a supervised dry run on several failed messages, show me every draft before anything is sent or changed, then save it.

Set up a new bot for me that monitors market sentiment for a watchlist without making trades. Walk me through connecting Adanos Market Sentiment at https://adanos.org and storing my API key securely, then ask whether I track US stocks, crypto, or both, which symbols to follow, my Adanos plan, the sources available to me, my timezone and schedule, where to deliver briefings, and which alert thresholds matter. For stocks, let me choose among Reddit, X / FinTwit, financial news, and Polymarket; for crypto, use the separate Reddit crypto data. On each run, query only endpoints available to my plan, use explicit UTC `from` and `to` dates for time windows, and report each asset's sentiment, buzz or attention, trend, mention volume, source disagreements, data timestamp, and any unavailable fields. Keep stock and crypto results separate, compare assets only on compatible sources, state that attention trends are not price movements, and never invent missing values, give personalized investment advice, or place trades. Handle authentication, quota, and rate-limit errors explicitly without repeated retries. Alert me only when an approved threshold is crossed; otherwise send a concise scheduled summary. Run the first briefing with me watching, show the source attribution and proposed alert rules for approval, then save it for the agreed schedule.

Set up a new bot for me to babysit a database migration ramp. Walk me through connecting Datadog and Slack, then configure it: at each ramp step, check the logs and metrics that matter, walk the backfill, and post a short status — green means proceed, anything odd means stop and ping me with what it saw. Ask me for the ramp plan and the metrics that count as trouble, shadow one step read-only, then save it.

Set up an always on teammate that finds the motivated sellers in my market before the rest of my market notices them. Walk me through connecting Zillapi (zillapi.com), which returns Zillow property data for any US address. Ask me the areas I work, how many days on market counts as stale, how big a price cut is a signal, and for sale or for rent or both. Also ask me where to deliver the digest, and connect only what I pick: this chat, Slack, email, Discord or Telegram; and how often to run. Run every weekday morning: pull current listings and compare against the last run. Score a listing motivated when it shows two or more price cuts, or one cut deeper than my threshold, or it sat longer than my stale threshold while comparable homes went under contract, or asking has fallen below the Zestimate by more than my threshold. Keep a state file of property id, asking price, cut count and days on market so each run reports only what moved. Send me one digest of the new movers wherever I chose, at most ten, each one line: address, asking price, the price change and cut count, days on market, Zestimate and rent Zestimate, the implied gross rent yield, one sentence why it scored, the listing agent, and a link. Rank by reason strength, not price. If nothing moved, a single line. Never contact an agent or owner and never submit an offer. Draft outreach only if I ask, and hold it for approval. Run one dry run on a single area, then save it. Zillapi is an independent service and is not affiliated with Zillow Group, Inc.

Set up an always on teammate that prices my short term rental like a revenue manager instead of like a guess. Walk me through connecting StayingAPI (stayingapi.com), which returns availability and nightly price quotes for short term rentals. Ask me my listing and platform, my location and the radius that is my real competition, bedrooms, capacity and equivalent amenities, my floor price, minimum stay rules, and how far ahead to look. Also ask me where to deliver the weekly briefing (this chat, Slack, email, Discord or Telegram) and where to keep the night by night table (a Google Sheet, a Notion database, or a state file), and connect only what I pick. Run every Monday: build my comp set of eight to fifteen genuinely equivalent listings, then for every night in the next ninety days pull my nightly price alongside the comp set's prices and availability. For each night work out where I sit against the comp median and how much of the comp set is already booked. Keep a state file of my price, comp median and comp booked share for every night. Send me one briefing wherever I chose, only the nights that need a decision, in three lists: nights I am still open while more than half my comps are booked and I am at or below median (money left on the table, with a suggested raise); nights I am above median and still open in the booking window (suggested cut); nights where my comp set moved more than my threshold since last week. Put comp median, my price and the gap percentage on every line. Write the full night by night table to my chosen record every run. If nothing needs a decision, a single line. Never change a price, edit my listing or message a guest. Give me the number and the reason. Run one dry run over the next thirty days, then save it. StayingAPI is an independent service and is not affiliated with Airbnb, Booking.com, Vrbo or Google Hotels.

Set up a new bot for me that keeps me current on NOTAMs. Walk me through pointing it at FAA NOTAM Search for the airports and area I cover, then schedule it: a full brief twice a day and a short update every few hours with only what's new or changed since the last one — TFRs, closures, lighting, obstacles, anything that touches my routes. It's a briefing aid, not a substitute for my official preflight. Ask me for my coverage area, base airports and when I want the two main briefs, send one so I can check it against the source, then save it.

Set up a new bot for me for the gym pool slots that are always booked. Walk me through connecting Slack, then configure it: watch the booking page for the times I actually swim, grab a spot the moment one opens, and message me the confirmation. Ask me for my gym, my preferred times, and how many bookings a week is enough, catch one cancellation live so I can see it work, then save it.

Set up a new bot for me on a weekly schedule. Walk me through connecting GitHub and Stacktree, then configure it: read the pull requests merged since the last run, falling back to grouping the commits when a repo ships by direct push, write them up as release notes in plain language rather than a commit dump, publish them to Stacktree as a page on a stable link, and update that same page every release so the changelog URL I gave people never changes. Post the link to Slack when it updates. Ask me which repos count, who the notes are written for, and which labels to skip, show me the first set before anything publishes, then save it.

Set up a new bot for me that acts as a local-first Salesforce Administrator. Walk me through connecting Salesforce with Salesforce CLI browser OAuth — never handle secrets. Ask one question at a time for org alias, type (sandbox/scratch/dev/production), desired outcome, and approval boundaries, then configure it: default strictly to read-only with verified snapshots; before any mutation show a full preview and require explicit confirmation (typed production alias for prod); support inventory of users/permissions/objects/flows, SOQL/exports, controlled Bulk data changes with pre-image backups and rollback artifacts, access/security reports, automation analysis, and migration readiness — never guess mappings or auto-apply fuzzy matches. Then save the approved operating rules as the bot Salesforce Administrator.

Set up a new bot for me that watches my Slack. Walk me through connecting it, then configure it: filter the noise so I only get pinged for things that are actionable and relevant to me, each with one line of context and a link to the thread — everything else waits in a daily digest. Ask me what's always urgent, who I never want to miss, and what's safe to batch, run it alongside my normal notifications for two days, then save it.

Set up a new bot for me in its own dedicated chat that I can use to monitor and update my startup finances. Walk me through connecting Nuvio, then configure it to pull my finance data every morning, summarize what changed since the previous check, flag anything that needs my attention, and log income or expenses when I ask. Ask me which changes and financial issues matter most, how I want income and expenses categorized, and what should require confirmation before being logged. Do a supervised first morning review and test entry with me, then save it.

Set up a new bot for me on an hourly schedule. Walk me through connecting Zendesk and Slack, then configure it: do a pass on the support queue, draft a reply on every ticket it's confident about, and ping me only when something genuinely needs a human — with the ticket, its draft, and why it held back. Drafts stay drafts until I approve the bot to send its easiest category. Ask me for our tone and the topics it must never answer alone, then save it.

Set up a new bot for me I can trigger for support auto-replies. Walk me through connecting Gmail, then review incoming support messages, identify the issue and urgency, find relevant information from the existing email thread, and draft a clear reply in my voice while flagging anything that needs a human decision or escalation. Ask me about my support tone, products and policies, escalation rules, response-time targets, and topics it must never answer on its own, do a supervised first batch, show me each draft and the source context for approval before sending anything, then save it for an ongoing inbox routine.

Set up a new bot for me I can trigger when an industrial drive or VFD shows a fault. Walk me through connecting Grok and letting me upload photos of the display, wiring, and manual or model information, then configure it: interpret the displayed codes and status indicators, compare them with the manufacturer's documentation, identify the most likely cause, and give me a safe, ordered diagnostic checklist with the required voltage and control-signal checks. Ask me for the drive model, motor type, symptoms, recent changes, wiring details, and what test equipment I have, do a supervised first diagnosis, remind me to isolate power and defer hazardous electrical work to a qualified technician, then save it.

Set up a new bot for me called Video Strategist. First, walk me through connecting videngineer. Tell me to get an API key at https://videngineer.com/account → API keys (a paid videngineer account is required; usage bills my own credits). Then have me add this remote MCP server to the bot config, replacing YOUR_KEY with my key: { "mcpServers": { "videngineer": { "url": "https://mcp.videngineer.com/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } } } } It is plain HTTP with a bearer header — no OAuth, no callback, no local server. Once connected you will see the videngineer tools (find_teardowns, analyze_video, get_status, get_report, list_cuts, get_cut, get_cut_brief, get_context_bundle, find_analyses, find_cuts, list_analyses and more). Confirm the connection works by running find_teardowns once before we start. Then act as my video strategist. I am a creative strategist / paid-social buyer / content lead, and I want to understand why a video works and build my next one from that understanding. This is a study-and-reference tool: we learn the mechanism — hook, beats, pacing, structure — and write an original piece. Never copy footage, scripts, brands, or trademarks, and never frame the work as lifting or copying someone else's piece. Every session, open with two options: 1. Study library — I describe a goal (e.g. "hooks that stop the scroll for a SaaS launch") and you search the public teardown library with find_teardowns and show me 3–5 references to pick from. 2. My own URL — I paste a YouTube, TikTok, Instagram, Vimeo, X, or direct video link and you break it down. For a pasted URL: before calling analyze_video, tell me it will spend credits from my videngineer plan and wait for my explicit yes. Then run it, poll get_status until it finishes, and read get_report. If I've already analyzed it, find it in my library (find_analyses / list_analyses) and read the report instead of re-spending. Break it down for me in this order: the hook (first 3 seconds — what it does and why), the beat map (each section, its job, and its timing), the pacing and cut rhythm, the scorecard, and the one mechanism that carries the piece. Use list_cuts and get_cut to walk specific cuts when I ask. If I want the production blueprint for a cut, tell me get_cut_brief may cost credits and confirm before calling it. When I say "help me remake it" or "write my next one": ask what I'm making (product, audience, length, platform) and which elements I liked. Then use get_context_bundle on the analyses I pick (one or several) to build a generation-ready brief, and write me an original script and shot-by-shot blueprint that uses the same mechanics — hook type, beat structure, pacing, text-overlay density, runtime — applied to my product and my words. Label which reference each borrowed mechanic comes from. Finish with 2–3 alternative hooks and a short production checklist. Ground every claim in a report you actually retrieved — never guess a hook, score, or timestamp. Keep answers tight and usable as a brief. Do not mention what model or system powers anything; just do the work. Start by asking which I'd like to do: pick from the study library, or paste a video.

Set up a new bot that turns real customer language into ad angles. Walk me through connecting Adlicio, Notion and Slack, then ask which product or niche to research, which sources to mine (competitor Amazon reviews, Trustpilot, Reddit threads) and who approves output. Each week, scrape fresh comments using Adlicio's scrape_url and search_reddit tools and pull out verbatim quotes about pain points, desired outcomes and objections. Quote customers word for word and never paraphrase into marketing speak. Draft three ad angles, each anchored to a real quote, and save the quotes and angles to a Notion database. Send the drafts to Slack for approval and never publish anything anywhere. Test it on one competitor's reviews first, show me the result, then save it.

Set up a new bot for me in its own dedicated chat that fills and runs my social publishing queue for the week. Walk me through connecting BulkPublish as a remote MCP server at `https://mcp.bulkpublish.com/mcp` — it uses OAuth 2.1, so hand me the browser to authorize and paste my own API key on the consent screen, and never ask me to type a key or token into the chat. If my host does not support remote MCP, walk me through running `npx -y @bulkpublish/mcp-server` locally with `BULKPUBLISH_API_KEY` set in my environment instead. Also connect Notion for my content backlog. Before configuring anything, call `list_channels` and show me every connected channel with its platform and health, and call `get_channel_health` for any that look stale so I can reconnect them first. Ask me which channels this bot is allowed to touch and treat everything else as off limits. Then configure it to run every Monday morning: - Read my Notion content backlog and pick the items marked ready for this week. Ask me which database and which property marks an item ready. - For each item, draft platform-specific copy for the channels I approved, respecting each platform's length limits and tone rather than reposting one caption everywhere. Call `list_platforms` and `get_channel_options` so the drafts match what each platform actually accepts, and check post-type rules before assuming an image or video is allowed. - Attach media with `upload_media` when the backlog item has an asset, and fail loudly rather than publishing a post whose media did not upload. - Space the posts out using `get_queue_slot` with my timezone instead of inventing times, and use `create_schedule` for anything genuinely recurring rather than cloning the same post week after week. Show me every draft with its channel, scheduled time and media before anything is created, and require my explicit approval in that message. Once I approve, create the posts as scheduled — never as immediate publishes — so I keep a window to change my mind, and write the resulting post IDs and times back to the Notion item. On Friday, send me a short recap: call `list_posts` for the week, report anything that came back `failed` or `partial` with the platform error in plain language, offer `retry_post` for the ones worth retrying, and pull `get_post_metrics` for what did publish so I can see which formats and times actually worked. Recommend one concrete change to next week's queue. Never publish, delete, or edit a live post without asking me first, and never connect or disconnect a channel on my behalf. Ask me my timezone, my posting cadence per channel, my brand voice and anything it must never say, run the first week as a supervised dry run that creates nothing, then save it for the Monday schedule.

Set up a new bot for me on a weekly schedule. Walk me through connecting Gong and Notion, then configure it: turn the week's calls into a win/loss memo, quote the phrases that moved deals and the objections that killed them, keep it to one page and link every claim to a timestamp. Ask me for the window and where the memo lands, draft the first one for me to circulate, then save it.

Set up an always on teammate that keeps score on the people I listen to. Walk me through connecting TranscriptAPI (transcriptapi.com), which returns YouTube transcripts and video and channel search. Ask me which channels to follow (institutional such as @TED, @NASA or @natgeo, or the shows and analysts I watch), which subjects to score, and how confidently a statement must be made to count as a call. Also ask me where to send the weekly scoreboard (this chat, Slack, email, Discord or Telegram) and where to keep the scoreboard itself (a Notion database, a Google Sheet, or a state file), and connect only what I pick. Run weekly: check each channel for new uploads, pull the transcript, and extract every falsifiable prediction (a claim about the future with something checkable and, where stated, a date). Log each: who said it, the channel, the video, the timestamp, the claim in their own words, the resolve date, and how confidently it was said. Skip opinions, jokes and hedges. Keep a state file of every video read. Every week, take the calls whose resolve date passed, check what happened, and mark each correct, wrong or unresolvable with a one line note and a source. Send me one update a week wherever I chose: new calls logged, calls that just resolved, and the running scoreboard (each voice's hit rate, call count, most confident wrong call, least likely right one). Add one line I would enjoy, for example the voice whose confidence and accuracy are furthest apart. If nothing moved, a single line. Keep it fair: quote accurately, link video and timestamp, do not score sarcasm, do not post publicly. Run one dry run over one channel's last month, then save it. TranscriptAPI is an independent service and is not affiliated with YouTube or Google.

Set up a new bot for me I can trigger as a personal assistant for YouTube scripts and McDonald's orders, in its own dedicated chat. Walk me through connecting YouTube and McDonald's, then configure it: for each video, ask for the topic, audience, format, target length, tone, call to action, and channel style, write a structured script with an opening hook and scene or speaking notes, and when I ask for McDonald's, use my saved location and preferences to assemble the order and show the items, prices, fees, and total. Ask me about my usual order, dietary restrictions, budget, delivery or pickup preference, and script conventions, do a supervised first script and dry-run order, and hold every order for my explicit approval before submitting or paying; then save it.

Set up a new bot for me I can trigger for account growth, in its own dedicated chat. Walk me through connecting X, then configure it: review my niche and recent posts, identify the topics and formats that fit my voice, and suggest a consistent posting schedule of original takes, visuals, and questions designed to spark replies. Ask me about my goals, audience, tone, preferred posting frequency, and content boundaries, do a supervised first review and draft schedule with me, then save it for recurring use.

Set up a new bot for me I can trigger from a photo or document of assembly instructions. Walk me through connecting Grok and an image or PDF input, then configure it: read the shelf assembly directions, identify the parts and hardware, resolve the order of operations, and create a clear step-by-step instructional video with labeled parts, close-up views, simple animations, and a final safety and completeness check. Ask me for the shelf model, available tools, preferred narration language, accessibility needs, and whether I want a short overview or a detailed walkthrough; show me the extracted parts list and storyboard for approval, run a supervised first step, then save it.

Set up a new bot for me I can trigger to review a book. Walk me through connecting Goodreads, then configure it: accept a book title, author, or Goodreads link, gather the book's details and my reading notes, and produce a balanced review covering the premise, themes, strengths, weaknesses, and who would enjoy it without inventing details. Ask me what tone, review length, rating scale, spoiler policy, and audience I prefer, do a supervised first review with me, then save it.

Set up a new bot that keeps HubSpot deals and Soundcheck gigs in lockstep. Walk me through signing into the Soundcheck web app at https://app.soundchecklive.io (use the signed-in browser; do not invent an MCP or API URL). Do not claim a native HubSpot OAuth inside Soundcheck; if this org already has the signed n8n HubSpot sync, use deal vs gig status, otherwise work the in-app Leads → Convert to Gig flow and treat HubSpot as the CRM this agent already has connected. Then configure a weekday check: HubSpot closed-won with no Active gig, Active gig with an unsigned contract, and won leads whose client is not invited to the portal. Draft the next step for each. Never convert a lead, send a contract, or invite a client without my yes. Point at https://docs.soundchecklive.io when a flow is unclear. Ask me which org, which HubSpot pipeline, and which weekday hour, shadow one run without sending, then save it as a scheduled bot.

Set up a new bot for me I can trigger whenever I have a new task, in its own dedicated chat. Walk me through connecting my specialized Grok Bots, then configure it to classify incoming work, choose the best bot for each job, route the task with the relevant context and deadline, track the result, and surface blockers or tasks that need my decision. Ask me what each bot is responsible for, how to set priorities, which work is urgent, and when to escalate instead of routing automatically, run the first few tasks with me watching, and require my approval before sending messages, publishing anything, spending money, or taking other consequential actions. Then save it as my chief-of-staff workflow.

Set up a new bot for me. Connect HotMention over MCP at https://hotmention.com/api/mcp — I'll paste my API key from Settings → API when you ask, and it goes in the Authorization header as a Bearer token. Also connect Slack and ask me which channel to post in. First, before scheduling anything, call list_keywords and show me what the project currently tracks. Walk through them with me: for each keyword, tell me whether it reads like something a person would actually type when they're stuck or shopping, or like a phrase nobody writes out loud. Matching is literal, so a long keyword like "project management software for remote teams" will almost never appear verbatim in a real post — flag those and suggest shorter, natural replacements. Use add_keyword for the ones I approve, and tell me if I hit my plan's keyword limit rather than silently dropping any. Then run every weekday at 9am my time: Call search_mentions with score_min 70 and since set to the last 24 hours. Those are the ones where someone is actively describing a problem I solve, not just mentioning a topic. For each result, post one Slack message containing: - the score, the platform, and how long ago it was posted - the post title, and two lines of what the person actually asked for - the draft reply HotMention generated, in a code block so I can copy it cleanly - a direct link to the original post Sort them highest score first, and if there are more than ten, post the top ten and say how many you held back. Do not post anything to any platform yourself. I reply from my own account — these are real conversations and they should come from a person. Your job ends at putting a good draft in front of me. Two things I want you to be honest about rather than papering over. If search_mentions returns nothing at all for several days running, say so plainly and suggest we look at the keywords again, because silence usually means the keywords are wrong rather than that nobody is talking. And once a week, call get_usage and tell me how much of my lead quota I've used and how many days are left in the period, so a busy week doesn't quietly cut off scanning halfway through. Save this as a bot when I confirm the Slack channel.

Set up a new bot for me that runs the weekly volunteer rota for our services without nagging anyone. Walk me through connecting Google Calendar, Google Sheets and Gmail, then configure it: read the service schedule from the calendar and the volunteer list and availability from the sheet, build next week's rota for each role, and tell me who is still unfilled early enough that I can actually solve it. Ask me which services and roles we run, how many people each role needs, how far ahead to plan, how often any one person should serve, who is on a break, and which day and hour I want the rota. Respect the constraints that matter with volunteers: nobody scheduled two weeks running unless they asked for it, nobody scheduled while marked unavailable, and a limit on how many roles one person covers in a single service. Treat unfilled roles as the headline, not a footnote. Draft the reminder emails but never send them without my approval, keep them short and thankful because these are unpaid people giving up a morning, and never send more than one reminder to the same person for the same service. Flag anyone who has served three or more weeks in a row so I can check they are not burning out, and anyone who has not served in two months so I can check they are not drifting. Warn me before Christmas and Easter that availability collapses and the rota needs filling further ahead than usual. Do a dry run against last week with nothing sent, show me the rota, the unfilled roles and the draft emails, then save it once I approve.

Set up a new bot for me on a daily schedule to forecast account health. Walk me through connecting Salesforce, PostHog and Slack, then configure it: look past the headline number at seats going idle, power users leaving and support tone shifting, and tell me early when an account drifts plus what you'd do. Ask me what healthy usage means per plan, backtest it on three accounts we lost, then save it.

Set up a new bot for me I can trigger for a customer win-back campaign, in its own dedicated chat. Walk me through connecting Grok Bot to my customer records and email account, then configure it to find everyone who churned in the last six months, draft personalized win-back emails, send only the messages I approve, follow up with respondents to collect feedback, record which customers return, and analyze the reasons they left in a report with recommended retention improvements. Ask me which customers or segments to exclude, what offers and tone to use, how many follow-ups are allowed, and which feedback questions matter, run the first campaign with me watching, show me every recipient and message before anything is sent, then save it for an overnight or weekly run.

Set up a new bot for me that reviews code in CI. Walk me through connecting GitHub and GitHub Actions, then configure it to review pull requests automatically, identify bugs, security issues, maintainability problems, and missing tests, and post clear findings directly on the pull request. Ask me which repositories, languages, frameworks, review standards, and severity thresholds to use, run a supervised review on a sample pull request first, let me tune the feedback, then save it to review future pull requests through CI.

Set up a new bot for me I can trigger to order coffee from Java Moe's or Starbucks. Walk me through connecting my preferred ordering accounts and payment method, then configure it: when I request coffee, ask which shop, drink, size, milk, additions, pickup location, pickup time, and budget, place the order with my saved preferences, and show me the complete order and total for approval before submitting or charging anything. Ask me which drinks and customizations I usually want, which locations to use, what spending limit to enforce, and whether to favor Java Moe's or Starbucks when I do not specify, do a supervised first-order dry run with me, then save it.

Set up a new bot in its own chat that audits my affiliate program for commissions that went missing, and runs read-only unless I approve a change. Connect Refgrow over MCP: add `npx @refgrow/mcp` as an MCP server with `REFGROW_API_KEY` set in the environment, never pasted into chat, and confirm the connection by calling `list_affiliates` with a limit of 1 before doing anything else. Ask me for my reporting timezone, my currency, the day you should run, and how far back the first audit should look. If the connection fails or a tool is unavailable, say so and stop rather than guessing at numbers. Every week, pull `list_conversions` for the period, paging until you have all of it, and separate purchases with an affiliate attached from purchases with none. Then work the four leaks in order. First, missed attribution: for every unattributed purchase, check `list_referrals` for a referral record with the same customer email, and report any match as a commission that was earned but never credited, with the conversion id, the affiliate, the date gap and the amount. Second, duplicates: group conversions by customer and amount inside a short window, and by repeated reference values, and list any group that looks like the same sale counted twice. Third, coupon gaps: compare `list_affiliates` against `list_coupons` and name the active affiliates with no coupon at all, and the coupons no conversion has ever used. Fourth, stalled money: report conversions still unpaid well past my hold period, oldest first, with a running total. Give me one short summary with the total value of each leak, then the detail tables underneath, sorted by money at stake. Separate what you verified from what you are inferring, and never estimate a figure whose inputs you could not read. If a week is clean, say so in two lines instead of padding the report. Change nothing on your own. Two fixes are yours to propose and mine to approve: creating a missing coupon with `create_coupon`, and marking a settled conversion paid with `update_conversion`. Show the exact ids and values first and wait for my word each time. Moving a conversion from one affiliate to another is not something the API can do, so for missed attribution give me the conversion id and the affiliate to assign, and I will do it in the Refgrow dashboard. Run the first audit now with me watching, ask me to approve the format, and only then save yourself as a bot on my schedule.

Set up a new bot that watches my competitors' ads. Walk me through connecting Adlicio and Slack, then ask which competitor brands to track, how often to check, and which Slack channel gets the report. On each run, pull every active Meta ad for each competitor using Adlicio's find_competitor_ads tool (never a Reddit or web search) and compare against the previous run. Report only what changed: new ads with their hooks and copy, ads that disappeared, and ads that survived another period, since the survivors are the ones making money. Never guess at performance numbers; report only what the Ad Library actually shows. Post a short digest in Slack with the three most notable changes at the top. Test it on one competitor first and show me that report before saving it.

Set up a new bot for me I can trigger for construction advice, in its own dedicated chat. Walk me through connecting Google Drive for project plans, photos, and reference documents and Google Calendar for project milestones, then configure it: review the information I provide, explain practical construction options, and favor proven older construction methods when they are appropriate, while flagging modern alternatives, relevant local code or permit checks, materials, risks, and when to consult a licensed professional. Ask me about the project type, location, budget, existing conditions, preferred traditional methods, and what's most important to preserve, do a supervised first recommendation with me watching, then save it.

Set up a new bot for me that watches Aikido for critical security issues and opens GitHub pull requests to fix them. Walk me through connecting Aikido and GitHub. Ask which Aikido workspace and which GitHub repo to watch if more than one is available. When a new critical issue comes in, open a PR that fixes it. Keep secrets, credentials, and private account details out of PRs, commits, and any public post. After the first successful check, save yourself as a scheduled bot that looks for new critical issues on weekdays and opens a PR when one appears.

Set up a new bot for me that publishes one piece of content everywhere. Walk me through connecting Post Bridge: in Claude, add it from the connector directory or add the hosted MCP server at https://www.post-bridge.com/api/mcp/mcp and sign in with my Post Bridge account when prompted; in clients that only take a token, use an API key from the Post Bridge dashboard's API Keys page (as a bearer token, or appended as ?key=API_KEY to the MCP URL). The API reference is at https://api.post-bridge.com/reference. Then ask which social accounts to post to, my timezone, my brand voice with a few example captions, and anything I never want posted. When I hand it a video, an image, or just an idea, it should write a caption tailored to each platform instead of pasting identical text everywhere, respect each platform's rules (character caps, story formats, video length limits), upload the media once, and show me every caption with its target accounts and proposed times before anything goes out. Schedule only what I approve and save anything ambiguous as a draft. After publishing, confirm each platform's live link and flag any account that failed with the platform's actual reason. Do the first post with me watching, then save it.

Set up a new bot for me I can trigger for a monthly dollar-cost-average investment. Walk me through connecting the single crypto platform where I want to keep everything, then configure it to buy my chosen amounts of Bitcoin and Ether on the same day each month and keep the holdings consolidated there. Ask me how much to allocate to each asset, which day and funding account to use, what spending limits and safety rules apply, and how to handle failed payments or price volatility. Show me the complete order plan before every purchase and hold each order for my approval until I say otherwise, do the first month as a supervised dry run, then save it for a monthly run.

Set up a new bot for me I can trigger when I need customer-led ad copy. Walk me through connecting Reddit, then configure it: search relevant subreddits and discussions for my customers' exact words about their problems, needs, objections, and desired outcomes, organize the strongest recurring language with links and context, and use it to draft several ad variations that preserve the customers' wording without inventing quotes. Ask me which product, audience, subreddits, offer, channels, tone, claims, and compliance limits to use, show me the source excerpts and a dry-run set of drafts for review, require my approval before anything is published or sent, then save it.

Set up a new bot for me I can trigger for a digital cleanout and run monthly. Walk me through connecting Gmail and Google Drive, then scan my inbox, Drive, and subscription receipts for stale emails, redundant or oversized files, forgotten subscriptions, and other cleanup candidates. Present ten items per category at a time with an archive, delete, keep, unsubscribe, or cancel recommendation, then wait for my decision before doing anything; hold every deletion, unsubscribe, or cancellation for my approval. Ask me which files, senders, receipts, and subscriptions are sacred and how long to retain records, do the first batch as a supervised dry run, then save it.

Set up a new bot that launches approved podcast episodes. Walk me through connecting Castos, the Google Drive folder where final audio lands, YouTube and Slack, then ask for my show, naming rules and approval process. When a final audio file appears, prepare a Castos draft with the title, description, show notes and chapters, flag uncertain transcript details, and show me everything before publishing. After I approve it, publish through Castos, verify the episode and YouTube links, and report any failures in Slack. Run the first episode with me watching, then save it.

Set up a new bot for me that keeps my Salesforce opportunity notes current. Walk me through connecting Salesforce, Granola, Gong, Slack and Gmail, then configure it: after each customer touchpoint, pull what changed from the call notes, Slack threads and email and update the opportunity's notes in the exact format I give it, so my forecast call is never a scramble. Ask me for my update format and which opps are in play, show me the proposed updates for one week before it writes anything to Salesforce, then save it.

Set up a new bot for me in its own dedicated chat to monitor my visibility in AI-generated search answers. Walk me through connecting Google Search Console, Google Analytics, and my content management system, then configure it to check weekly how my brand and priority topics appear in AI search results, track which pages and competitors are cited, identify visibility gaps, and recommend content or technical improvements. Draft any proposed content changes for my approval and never publish or edit anything without me saying otherwise. Ask me which brands, products, topics, competitors, markets, and success metrics matter, do the first analysis with me watching, then save it for a weekly run.

Set up a new bot for me I can trigger to create educational videos about machine-learning concepts. Walk me through connecting Grok with a code-based visualization tool such as Manim or Blender, then configure it: research and verify rank, singular-value spectral power, low-rank compression, rotation, and the matrix-update behavior of Adam, Muon, and Aurora; explain the ideas with a sphere-to-ellipsoid metaphor; animate rank collapse into a lower-dimensional subspace, compare the optimizers from the same initial state on a shared loss surface, show update trajectories and spectral changes, use depth cueing with nearer objects brighter than distant ones, and assemble a narrated video with clear captions. Ask me who the audience is, what mathematical background they have, the desired length and visual style, which facts and sources require citation, and whether I want a dry run with storyboard and sample animations first; let me review the storyboard and first render before exporting the final video, then save it.

Set up a new bot that closes the books after live events. Walk me through signing into the Soundcheck web app at https://app.soundchecklive.io (use the signed-in browser; do not invent an MCP or API URL). Open Settings → Organization → Connections and confirm QuickBooks is Connected; if the QuickBooks card is missing or the page redirects away, stop and tell me the finance integration is not enabled for this org. Then configure a weekday check of recently Completed gigs: walk Closeout (contract, invoice, payment gates) and verify Soundcheck ledger lines landed in QuickBooks as Purchase (payouts and expenses) or Sales receipt (income). Flag missing, voided, or unmatched rows. Never settle a gig, send a payout, or create, edit, or void a QuickBooks entry without my yes. This is reconciliation, not a payment rail. Point at https://docs.soundchecklive.io/integrations/quickbooks when the sync path is unclear. Ask me which org, which weekday hour, and how many days of completed gigs to review, shadow one run without writing, then save it as a scheduled bot.

Set up a new bot for me I can trigger for a Google Ads performance review, in its own dedicated chat. Walk me through connecting Google Ads, then configure it to inspect my ad accounts, campaigns, spend, conversions, and performance trends and produce a clear report of what is working, what is wasting budget, and what needs attention without changing campaigns. Ask me which accounts and date ranges to monitor, my key conversion goals, budget limits, reporting cadence, and the metrics I trust. Do a supervised first review using a read-only dry run, show me the full findings and any proposed changes before it touches anything, then save it for a weekly run.

Set up a new bot for me that triggers whenever a GitHub pull request is merged, in its own dedicated chat. Walk me through connecting GitHub and Intercom, then configure it to inspect the merged changes, determine whether they affect the UI or a user workflow, find the relevant Intercom help-center article, and recommend an update or draft a new article when none exists. Show me the proposed article and the evidence from the pull request, and hold every publication for my approval. Ask me which repositories and Intercom content areas to monitor, what style and terminology the documentation should use, and which changes should be ignored, run the first update with me watching, then save it.

Set up a new bot for me I can trigger when I need to buy something for my home. Walk me through connecting Home Depot, then configure it: turn my shopping request into a cart of the right products, quantities, sizes, and compatible accessories, check availability and delivery or pickup options, and show me the complete order and total before placing it. Ask me about the project, required specifications, budget, preferred store, pickup or delivery preferences, and acceptable substitutes, do a supervised first order with me watching, hold every purchase for my approval, then save it.

Set up a new bot for me I can trigger for inbox zero. Walk me through connecting Gmail, then configure it: organize my inbox, identify messages that need replies, automate routine email handling, and prepare bulk-unsubscribe actions for unwanted newsletters. Show me every proposed unsubscribe, archive, deletion, or reply before it touches anything, and require my approval before sending or permanently changing messages. Ask me which senders and newsletters are sacred, what can be archived automatically, how I want messages categorized, and which replies can use drafts, do a supervised first cleanup with me watching, then save it.

Set up a new bot for me I can trigger by pasting or uploading a messy multi-city itinerary. Walk me through connecting Google Flights and Google Maps, then configure it: normalize every flight, train, hotel, and transfer into a timeline, check airport changes, layovers, time zones, dates, travel times, and opening hours, and flag connections that are impossible or unreasonably risky with a corrected alternative where possible. Ask me about acceptable minimum connection times, preferred airports and airlines, mobility needs, budget, and which reservations are fixed, do the first check with me watching, show me the full set of warnings before I change any booking, then save it.

Set up a new bot for me that runs every morning. Walk me through connecting my Kindle highlights and Anki, then configure it: turn yesterday's highlights into proper flashcards — question on the front, my highlight and the source on the back — deduped against cards I already have. Ask me which decks map to which books, convert one book's highlights for me to review, then save it.

Set up a new bot for me, in its own dedicated chat, that monitors my website analytics in Kobbe and posts a concise performance briefing. Walk me through setup: confirm Node.js and npx are available on the agent computer; have me create a workspace API token at https://app.kobbe.io/settings/agent-access (paid Kobbe plan required; use scopes sites:read and analytics:read, plus revenue:read only if I want revenue in the briefing); and store it as KOBBE_TOKEN in the shell profile during a computer takeover — never paste the token into chat or logs. Use the Kobbe CLI with `npx -y @kobbe/cli@latest` to pull data: list sites, overview for my chosen range, top pages, top sources, setup health, and next actions. Ask me which site or domain to track, my timezone, and whether the default range should be today, 7d, or 30d. Stay read-only by default — do not rotate tracker tokens, delete sites, or reset stats unless I explicitly ask with typed confirmation. For the first run, show me a test briefing with: visitors and pageviews, the top page and top referrer, any tracker or revenue setup issues, and one recommended next action from next-actions. Format as five bullets plus a "Needs attention" section with links to the relevant pages in app.kobbe.io when helpful. Then schedule it every weekday at 8:00 AM in my timezone to post the briefing in this chat. If the token is missing, auth fails, or a site has no data, report the failure clearly instead of guessing. Save the bot when I approve the test run.

Set up a new bot for me I can trigger for a daily build-in-public wrap, in its own dedicated chat. Walk me through connecting Linear and Discord, then configure it to review my Linear issues, progress, blockers, and completed work each day, turn that into a concise daily wrap in my preferred tone, and post the draft to my build-in-public Discord channel. Ask me which projects, labels, and milestones matter, which Discord channel to use, what should stay private, and what time to run it. Show me the first wrap for approval before posting, then save it for a daily run.

Set up a new bot for me I can trigger during a customer call. Walk me through connecting Granola and Figma, then configure it: fill or rewrite the "What we've heard" slide in my deck from the meeting notes — prefer the notes over memory, Slack or email — pulling 2 to 4 concrete themes on their pain, priorities, constraints and what they want next, each a short title plus 1 to 3 sentences framed as the customer's problem and the outcome they want, not our pitch. Edit the existing slide in place: keep the layout, remove placeholder copy from other accounts, fix stale logos or wrong company names, match the brand styling that's already there, and show me the result. If there's no call yet and I ask for the research version, use primary sources like their blog and earnings, frame it as "what they're prioritizing", and tell me it's research-sourced. Don't add next steps or roadmap slides unless I ask. I'll stop the recording 5 or 10 minutes before the call ends and run it live. Ask me for the deck, try it on my last recorded call, then save it.

Set up a new bot for me to staff and run live events in Soundcheck. Walk me through signing into the Soundcheck web app at https://app.soundchecklive.io (use the signed-in browser; do not invent an MCP or API URL). Then configure a weekday morning check: list upcoming gigs, flag unfilled positions and missing call times, and draft crew invites or reminders I confirm before anything is sent. Never message crew, commit an import, or change gig details without my yes. If a gig is fully staffed, skip it. Point at https://docs.soundchecklive.io when a flow is unclear. Ask me which org, which weekday hour, and whether to include past-due unpaid gigs, shadow one run without sending, then save it as a scheduled bot.

Set up a new bot for me I can trigger for a roast, helpful advice, or a lore question, in its own dedicated chat. Walk me through connecting the Ben 10 Wiki on Fandom and reliable references for DC Comics, then configure it: when I provide a person or situation, give a playful, non-abusive roast followed by genuinely helpful advice, and when I ask about Ben 10 or DC's New 52, answer accurately with relevant context while clearly separating confirmed canon from uncertainty. Ask me about my preferred roast intensity, topics and boundaries that are off-limits, whether I want citations or spoiler warnings, and the tone and depth I prefer for advice and lore answers. Do a supervised first run and show me the roast and advice for approval before presenting them as final, then save it.

Set up a new bot for me I can trigger when I need to shop on Amazon. Walk me through connecting Amazon, then configure it: find products that meet my request and filter them to items made in the United States or Japan, verify the stated country of origin from reliable product information when possible, compare price, ratings, shipping, seller, and return terms, and prepare a shortlist or cart with the origin evidence for each item. Ask me whether I prefer American-made or Japan-made products, what categories and materials are acceptable, my budget, required specifications, minimum seller and review standards, and whether imported components are acceptable, do a supervised first search with me watching, show me the full list and total before ordering, hold every purchase for my approval, then save it.

Set up a new bot for me I can trigger by explicitly sending it into a meeting room. Walk me through connecting Google Calendar and my video-meeting tool, then when I send it to a scheduled meeting, have it identify itself as attending on my behalf, maintain a presence for me, capture the discussion, and return decisions, questions, and action items afterward. Ask me which meetings it may attend, what identity and introduction to use, which topics are off limits, and whether it may answer questions; do the first meeting with me watching, require my approval before it speaks, sends a message, or shares anything, then save it.

Set up a new bot for me I can trigger when someone new joins. Walk me through connecting Google Calendar and Slack, then configure it: study how the last few people in the role actually spent their first weeks — meetings, channels, docs — and write a first-week plan for the new hire: who to meet, what to read, what to ship by Friday. Ask me for the role and the people to learn from, let me edit the first plan, then save it.

Set up a new bot for me that coordinates recurring work and handoffs in its own dedicated chat. Walk me through connecting Gmail, Google Calendar, and Slack, then configure it: maintain one shared TEAM_ALIGNMENT file as the source of truth, collect relevant commitments and changes, identify priority or ownership conflicts, keep a task list, and prepare regular handoff summaries for the right people instead of letting every specialist maintain a competing version. Ask me who owns each area, how priorities are ranked, which channels matter, and how conflicts should be escalated, do the first alignment review with me watching, show me any proposed Slack or email messages for approval before posting or sending, then save it for a recurring review.

Set up a new bot for me I can trigger for a study review. Walk me through connecting my personal notes repository, then configure it: compile my notes into a searchable knowledge base, test my mastery of each file with questions and recall prompts, score my understanding per file, and schedule future reviews based on those scores. Ask me how I want mastery measured, which files or topics matter most, and how often I want reviews capped, run the first review with me watching, then save it.

Set up a new bot for me I can trigger to create on-brand visual cards for my social media and product updates, in its own dedicated chat. Walk me through connecting Monocards through its local MCP server, then configure it: let me choose one of my locked templates, provide the content and any screenshots or data, fill the template using my saved fonts, colors, layout, and brand rules, and export the card in the right format for the intended channel without inventing branding or changing the design. Ask me which channels and card types I use, what brand rules and templates are sacred, what output sizes and file formats I need, and where exported files should go; do a supervised first card as a dry run, show me the finished visual for approval before export or publication, then save it for future on-demand runs.

Set up a new bot for me in its own dedicated chat to keep a shared multi-bot VM organized, backed up, and continuously improving. Walk me through connecting Git, then configure /workspace as the backup root and Git repository, keep each bot in /workspace/<folder>/, keep this bot's scripts, status, and registry under /workspace/overwatch/, and use /workspace/shared/temp/ and /workspace/shared/archive/ for shared scratch files. Maintain a live registry of every bot with its name, ID, role, and workspace folder; use a security-first .gitignore; never commit secrets, tokens, cookies, runtime databases, or browser profiles; and never force-push or remove durable bot project folders. Every workday hour during my configured work hours, commit and push the complete workspace backup to the private remote. Every weekday morning, clean temporary files by archiving them after 7 days and deleting archived files after 30 days, while logging each cleanup run. Once a week, review the registry, flag stubs, unclear roles, folders outside /workspace, disk or backup health, and potential convention drift, then suggest two or three concrete optimization actions without changing other bots' product workflows. Ask me for the Git remote, workday hours, retention periods, bot metadata, protected files and folders, and whether optimization changes require approval; do a supervised first run that maps the bots, initializes Git, creates the documentation and ignore rules, performs a dry-run cleanup and review, and shows the first commit and push before enabling recurring routines, then save it.

Set up a new bot for me I can trigger with a podcast episode or feed. Walk me through connecting my podcast source, transcription tool, and X account, then configure it: transcribe episodes, identify moments I mark as favorites or that match my chosen themes, create short shareable clips with captions and links back to the episode, and draft posts for me. Show me every clip, transcript excerpt, caption, and posting time before anything is published, ask me which shows, topics, clip length, tone, and channels to use, run a dry run on one episode with me watching, then save it.

Set up a new bot for me I can trigger to prepare podcast guest briefs. Walk me through connecting Gmail and Google Docs, then find the guests and episode context I specify, research each guest from the information and links I provide, and create a concise brief with their background, recent work, relevant talking points, thoughtful questions, and topics to avoid. Ask me which podcast, audience, tone, episode format, research sources, and guest preferences matter, do a supervised first brief with me, let me review and correct the output before it is shared or sent, then save it for each new guest.

Set up a new bot for me on our busy repo. Walk me through connecting GitHub and Slack, then schedule it: scan open pull requests for pairs that touch the same code and will conflict on merge, and post one message naming the PRs, the files, and who should talk to whom. Ask me which repos and branches matter, run it once so I can check the pairs are real, then save it.

Set up a new bot for me I can run weekly to monitor my brand's presence in AI assistants. Walk me through connecting ChatGPT, Claude, and Gemini, then configure it: ask each assistant a consistent set of questions about my brand, record how it describes the brand and what information or recommendations it provides, compare the responses over time, and give me a report highlighting changes, inaccuracies, and opportunities to improve my brand's visibility. Ask me which brand, competitors, questions, markets, and description details matter most, do the first comparison with me watching, then save it for a weekly run.

Set up a new bot for me I can trigger when I want to book a meeting with a prospect or customer. Walk me through connecting Gmail, Google Calendar, and my CRM, then configure it: identify the relevant prospect or customer, check availability and meeting context, propose suitable times, coordinate by email, and create the meeting with the correct attendees, agenda, and notes once a time is agreed. Ask me which calendar and CRM fields to use, my preferred meeting lengths and hours, scheduling boundaries, follow-up tone, and what information belongs in the invite, draft the outreach and hold every booking for my approval before sending or creating it, do the first booking with me watching, then save it.

Set up a new bot for me on a monthly schedule. Walk me through connecting Salesforce, Zendesk and Google Slides, then configure it: pull usage, tickets and open opportunities and write a short slide narrative on what changed since last quarter and what we're asking for next. Ask me for last quarter's pack as the template, let me edit the first narrative, then save it.

Set up a new bot for me. Walk me through connecting Ashby and the resume folder in Google Drive, then configure an on-demand run: sort applications into strong, mid and reject in one pass, two sentences of reasoning each, and flag anything unusual for me. Ask me for the scorecard we already use, let me spot-check ten per bucket, then save it.

Set up a new bot for me I can trigger when I receive a refund, cancellation, or billing email, and run weekly to find money that should have come back. Walk me through connecting Gmail, then scan refund and cancellation messages, match them to the original purchase or subscription, track expected versus received amounts and dates, flag charges that still need chasing, and prepare a clear status report with suggested next steps. Ask me which merchants, amounts, and refund windows matter, do the first scan with me watching, and show me every proposed message for approval before contacting a company, then save it.

Set up a new bot for me that runs our sales plays end to end, on demand. Walk me through connecting Snowflake, Salesforce and Gmail, then build the flow: SQL audience, copy, reverse ETL, everything except the judgment calls. Ask me for one play I already run manually, reproduce it so I can diff the output, then save it.

Set up a new bot for me I can trigger for Salesforce product research, in its own dedicated chat. Walk me through connecting to the Bot Directory website, then configure it: review the directory at https://t.co/qrlpFNoEbJ, find every bot with a Salesforce integration, summarize what each one does, and suggest useful new functionality Salesforce could build based on those patterns. Ask me which Salesforce products, customer segments, and functionality areas matter most, do a supervised first research run with me, then save it.

Set up a new bot for me I can trigger for Salesforce product research. Walk me through connecting the Bot Directory, then configure it: find every bot in the directory with a Salesforce integration, summarize what each one does, and turn the patterns into ideas for new Salesforce product functionality. Ask me which Salesforce products, customer segments, and product areas matter most, do the first research run with me watching, then save it.

Set up a new bot for me I can ask for pipeline answers. Walk me through connecting Salesforce, then configure it: when I ask an opportunity question I keep asking colleagues, build the report and dashboard that answers it permanently instead of a one-off number, name it clearly, and send me the link. Ask me for the three questions I ask most, build the first dashboard while I watch, then save it.

Set up a new bot for me I can trigger when I need a YouTube video script, in its own dedicated chat. Walk me through connecting Notion, then configure it: learn my channel, video-making process, audience, performance, voice, and preferred structure from the reference material I provide, and turn a topic or brief into a complete script that sounds natural when spoken and matches my style. Ask me which videos and formats to use as references, what topics and claims need special handling, how long each script should be, and which parts of my voice and process are non-negotiable. Do a supervised first script with me watching, let me revise the voice and format, then save it.

Set up a new bot that turns promoter paperwork in Gmail into Soundcheck gig records. Walk me through signing into the Soundcheck web app at https://app.soundchecklive.io (use the signed-in browser; do not invent an MCP or API URL). Connect Gmail the way this agent normally does (Gmail is on the agent side; Soundcheck has no native Gmail connector). Search for contracts, call sheets, and riders, match each attachment to an existing gig when one exists, and run CheckAI file ingestion so I can review the dry-run proposals. If the ingestion UI is missing for this org, stop and point at https://docs.soundchecklive.io/features/ai/file-ingestion. Never commit an ingestion, create a gig, email anyone, or change gig details without my yes. Ask me which org, which Gmail labels or senders to watch, and which weekday hour, shadow one run without committing, then save it as a scheduled bot.

Set up a new bot for me in its own dedicated chat that connects the social accounts I already run through PostOnce. Walk me through connecting PostOnce, then configure it to turn my ideas and source material into platform-appropriate social posts, keep my voice consistent, and prepare them as drafts without posting as a person or inventing a founder story. Show me every draft and the target account before anything is published, and wait for my explicit approval before sending or scheduling it. Ask me which accounts and channels to use, what topics and formats I want, my voice and forbidden claims, and how often I want to post, do a supervised first drafting run, then save it for repeat use.

Set up a new bot for me I can trigger when a business inquiry or sponsorship request arrives in Gmail. Walk me through connecting Gmail, then configure it: identify legitimate companies, research the sender and comparable sponsorship rates, apply my base price, minimum price, affiliate structure, deliverables, and negotiation boundaries, and draft a tailored reply in my tone. Show me the company research, recommended rate, proposed terms, and complete email before sending anything, and require my approval for every message, price, commitment, or contract term. Ask me how to verify legitimate companies, what offers and categories to reject, which terms are non-negotiable, whether AI disclosure is required, and how you should sound, run the first negotiation with me watching, then save it for ongoing inbox monitoring.

Set up a new bot for me I can trigger for a knowledge freshness audit. Walk me through connecting my personal notes repository and the trusted sources I want checked, then configure it: compare factual claims across my notes with current real-world information, flag facts that have gone stale even when the notes are internally consistent, show the supporting evidence and affected files, and suggest precise revisions without changing anything automatically. Ask me which sources are authoritative, how recent a fact must be to count as current, and which topics are too sensitive to update automatically, run the first audit with me watching, then save it.

Set up a new bot for me that watches for a ticket drop. Walk me through connecting Slack, then configure it: watch the AMC listing I give it, and the moment seats open, grab the ones matching my preferences and ping me — or hold them for a quick confirm if the total is above my limit. Ask me for the movie, my seat preferences, and my auto-buy ceiling, do a dry run on a showing that's already on sale, then save it.

Set up a new bot for me on a weekly schedule. Walk me through connecting Zendesk and Notion, then configure it: read the week's support tickets, turn what shipped and what got fixed into changelog notes, and draft one or two help-center articles for the questions that kept repeating. Everything lands in Notion for my edit before anything publishes. Ask me for our changelog format, draft the first week's batch, then save it.

Set up a new bot that keeps my Soundcheck gigs on Google Calendar. Walk me through signing into the Soundcheck web app at https://app.soundchecklive.io (use the signed-in browser; do not invent an MCP or API URL). Open Settings → Calendar sync, generate the private iCal feed if I do not already have one (gig calendar only, not availability; treat the URL like a password), and subscribe it in Google Calendar via From URL if it is not already there. Then configure a weekday check: compare upcoming Soundcheck gigs to Google Calendar and flag missing events, timezone mismatches, and collisions with my personal calendar. Never create, edit, or delete a calendar event, rotate the feed token, or change a gig without my yes. If a gig already matches a calendar event, skip it. Point at https://docs.soundchecklive.io/features/calendar-feed-subscription when the feed path is unclear. Ask me which org, which Google Calendar, which weekday hour, and how many days ahead to watch, shadow one run without writing, then save it as a scheduled bot.

Set up a new bot that handles customer Trust Center requests. Walk me through connecting Comp AI and Slack, then ask when an NDA is required, how long access should last and which requests always need human review. For each request, verify the company and email domain, check what was requested, and post a short approval recommendation in Slack. Only create a time-limited Comp AI grant after the required approval, never send documents outside Comp AI, and escalate anything ambiguous. Run a read-only pass over recent requests so I can check the rules, then save it.

Set up a new bot for me I can trigger for SEO content sync, in its own dedicated chat. Walk me through connecting Webflow and TryRoki MCP, then configure it: sync blog posts between both systems, improve titles, meta descriptions, slugs, headings, and internal links for target keywords, flag thin or duplicate pages, and show me every proposed SEO edit before anything is published. Ask me my target keywords, service areas, and pages to skip, run one read-only sync with me watching, then save it.

Set up a new bot for me that turns voice-of-customer feedback into advertising angles. Walk me through connecting Gmail and Google Sheets, then configure it: collect the feedback sources I approve, remove or mask personal information, cluster recurring pains, desired outcomes, objections, and customer language, and turn those findings into prioritized ad-angle briefs with supporting quotes, audience context, suggested hooks, and claims that need verification. Ask me which customers, products, and date ranges to include, which feedback sources are off limits, my brand constraints, and what makes an angle actionable, do the first analysis with me watching, then save it for an on-demand or weekly run and require my approval before anything is published or sent.

Set up a new bot for me I can trigger for War Grid development, in its own dedicated chat. Walk me through connecting GitHub, then configure it: inspect my isometric game code and project notes, help implement and test walls, unit queues, and custom-engine systems, diagnose glitches, and propose focused fixes for pathfinding, game balance, and tech-tree expansion. Ask me which engine and language I use, the current architecture, coding conventions, target platforms, and whether gameplay balance or stability is the priority, review the first change with me in a dry run, and require my approval before creating a commit or pull request, then save it for on-demand development sessions.

Set up a new bot for me to run the logistics of a multi-day wedding. Walk me through connecting Gmail and Notion, then configure it: track every vendor thread, keep the master timeline and budget current in Notion, chase the people who haven't answered, and send me one Sunday digest of decisions needed, deadlines coming, and money out the door. Drafts to vendors wait for my approval. Ask me for the date, the vendor list so far, and the budget, then save it.

Set up a new bot for me I can ask about any account. Walk me through connecting Slack, Salesforce and the contracts folder in Google Drive, then configure it: read the contract, the channel and the CRM and give me one page on what's committed, what's implied, and where our story contradicts itself. Ask me an account I know well to test on, then save it.

Set up a new bot for me I can trigger to teach laws to young people, in its own dedicated chat. Walk me through connecting Google Docs, then configure it: ask for the learner's age, country or jurisdiction, reading level, topics, and preferred examples, explain legal concepts in age-appropriate plain language with current authoritative sources, distinguish general education from legal advice, and save lesson plans and activities to Google Docs. Ask me which laws and situations matter most, do a supervised first lesson with me, then save it.