Michael | AI + Agents

I've seen a few people struggling to manage multiple projects with Grok Bot. Here's the setup I'd recommend after working through it with my Bot team. The secret is to stop using chats as your project management system. Instead, use Grok Bot's Pages feature. One Page per project. One routine to keep it updated. Every Bot reads the Page before starting work and updates it when finished. Here's the exact setup you can copy. Paste this into your Chief of Staff: "Set up a Page-based project management system for my Grok Bot team. 1: PROJECT PAGES - Create one Page for each project, containing its goal, current status, next actions, task owners, deadlines, decisions, blockers and an update log showing which Bot changed what. 2: MASTER INDEX - Create a Projects Page listing every active project, its status and the next action. This becomes my single place to see what's happening across all projects. 3: READ FIRST, UPDATE LAST - Every Bot must read the relevant project Page before starting work and update that same Page when finished. Never create duplicate Pages. Don't mark work complete without checking the actual result. 4: SHORT CHATS - Use fresh chats for individual tasks instead of maintaining one enormous project conversation. The Page holds the project history, decisions and context. 5: DAILY HEARTBEAT - Create one weekday routine per project. Check relevant sources such as email, GitHub, Notion or calendars, verify progress and update the project Page and master index. 6: EXCEPTION REPORTING - Only notify me when something is blocked, overdue, needs my decision or changes status. Otherwise, keep the Pages updated without interrupting me. 7: PROJECT CLOSURE - When a project finishes, mark it Closed, record the outcome and lessons learned, and pause its heartbeat routine. Never send, purchase, publish or delete anything without my approval. Clearly flag anything unverified. Before creating anything, show me the proposed projects, their information sources and the routines you'll establish. Wait for my approval." My recommendation? Start with one project for seven days. If your Bots keep its Page current and you no longer need to dig through old conversations to understand what's happening, expand it to the rest. Your chats are for doing the work. Your Pages are for remembering and managing it.

If Grok Bot still needs you to manage every step, check these five setup fundamentals. Who owns the job? What does finished look like? Where should it check the facts? Has the task worked before you automate it? Which decisions need you? Here’s the framework I’d use if I were starting again.

A text message can start a Grok Bot job without you opening the app. I tested it with an iMessage from my wife: a keyword triggered an iPhone Shortcut, which started a Grok Bot routine through a webhook. Here’s the seven-step setup to try it yourself. 👇

If I were introducing Grok Bot into a business, I wouldn’t start by asking what jobs AI could do. I’d look for where people are repeatedly acting as the glue between information, software and an outcome. - A customer question becomes a search through account records. - A sales call becomes a follow-up email and a customer record update. - An invoice becomes a check against an order and an approval request. Different departments. The same pattern. Someone has to gather information, move between tools and get the job finished. That’s where I’d start. Here’s the five-step framework I’d use to find the first workflow, prove its value and then expand: 1 - MAP THE REPEATED WORK List five jobs your team handles every week. For each, record what starts it, which information and tools it needs, how long it takes and what counts as finished. Be specific. “Help with sales” is too broad. “After each sales call, prepare the follow-up email, record the agreed next steps and propose updates to the customer record” gives you something you can test. 2 - CHOOSE YOUR FIRST WORKFLOW Look for a job that happens frequently, has accessible information, produces an easy-to-check result and has manageable consequences if something goes wrong. Estimate how much team time it consumes each week. Choose one useful, bounded workflow. 3 - RUN A SMALL PILOT Start with 10 representative cases. Connect the tools or provide the files Grok Bot needs, and confirm it can access the information. Include ordinary requests, missing information and an unusual situation. Show Grok Bot examples of acceptable work. Define when it should continue, ask a question or hand the job back. Keep customer messages and consequential changes behind your approval during the pilot. Record what it completed correctly, what needed fixing and where it got stuck. 4 - MEASURE THE NET BENEFIT Compare the old process with the pilot. Count your review time, corrections and supervision. Include running costs and whether the work met your standard. A job that previously took 20 minutes and now takes 5 minutes to review saves 15 minutes of team time, before running costs. A job that takes 25 minutes to repair needs more work. Decide whether to expand, revise or stop based on the result. 5 - EXPAND INTO THE NEXT CONNECTED JOB Once the first workflow is reliable, add a related step that can reuse its information. For example, after sales follow-ups are working, test preparing an onboarding pack when a deal is confirmed. Then test tracking the information the new customer still needs to supply. Check the result at each stage before expanding again. Your first adoption plan only needs four things: One workflow. A small pilot. A measurable benefit. The next connected job. The biggest opportunity isn't necessarily replacing an entire job. It's removing the repetitive work that sits between your people, their tools and the finished result.

Most people are barely scratching the surface of what Grok Bot can do. Here are five instructions I'd give your Chief of Staff to take your setup from beginner to power user. Each one unlocks a different capability, and you can copy the instructions directly into your Chief of Staff. 1 - MAKE GROK BOT WORK WITHOUT BEING ASKED Most people either message Grok Bot or set up scheduled routines. But Grok Bot can also start working when something happens in another app. An iPhone alarm stops. An important email arrives. A customer submits a form. These events can trigger work automatically through supported integrations, automations and webhooks. Tell your Chief of Staff: "Find five recurring jobs in my life or work that could start automatically when something happens. Investigate triggers from iPhone Shortcuts, email, webhooks and connected apps. Rank them by usefulness and ease of setup. Show me how we'd implement the best one. Don't activate anything without my approval." 2 - TURN SUCCESSFUL WORK INTO REUSABLE SKILLS Every time Grok Bot completes a job successfully, there's an opportunity to make that process repeatable. Instead of explaining the same job over and over, turn the method into a skill with clear instructions, inputs and checks. Tell your Chief of Staff: "Review the recurring jobs you've completed for me. Identify five that could become reusable skills. For each, define when to use it, what information it needs, the steps involved, how to check the result and when to ask for approval. Recommend the best one to build and test first." 3 - MAKE YOUR CHIEF OF STAFF MANAGE A TEAM OF BOTS You shouldn't have to coordinate every specialist bot yourself. Your Chief of Staff can become the central coordinator, delegating work, collecting results and bringing decisions back to you. Tell your Chief of Staff: "Review the work I regularly give you. Identify which jobs you should own and which would benefit from specialist bots. Recommend a small team with clearly defined responsibilities. Design how you'd delegate tasks, track progress, check results and report exceptions. Don't create new bots without my approval." 4 - MAKE GROK BOT FIND PROBLEMS IN ITS OWN SETUP As your setup grows, you can end up with failed routines, duplicated work, outdated instructions and unfinished jobs. Instead of discovering problems yourself, give your Chief of Staff responsibility for checking the system. Tell your Chief of Staff: "Design a weekly health check for my Grok Bot setup. Look for failed or missed routines, unfinished tasks, duplicated work, stale information and recurring corrections. Use records you can actually access and flag anything you can't inspect. Give me the five most important fixes ranked by impact. Make no changes without approval." 5 - TEACH GROK BOT TO WORK MORE EFFICIENTLY Not every job needs Grok Bot to open a browser and click through software. Sometimes a connected app, direct API or simple script can do the job more efficiently. Choosing the right method can reduce unnecessary work, failures and usage. Tell your Chief of Staff: "Review five recurring jobs that require multiple tool actions. Compare whether connected apps, APIs, scripts, browser automation or computer use would be the most appropriate method. Prioritise reliability, security and efficient usage. Recommend improvements and explain what we'd need to test before changing anything." THE BIGGER PICTURE These five upgrades change how you use Grok Bot. 1 - It starts working when something happens. 2 - It remembers successful methods through reusable skills. 3 - It coordinates other bots instead of making you manage them. 4 - It helps identify problems before they keep repeating. 5 - It chooses better ways to complete work. You move from constantly telling Grok Bot what to do toward building a system that can organise, execute and improve work with less intervention. Start by giving your Chief of Staff instruction number one, then work through the remaining four. You don't need to implement everything at once. Each upgrade makes your setup more capable.

I just reduced Grok Bot's token usage by 40.6% on the same task by changing how I instructed it. Instead of telling it what to do, I taught it how to do it. I wanted to experiment with two different ways of getting Grok Bot to complete the exact same job. The task was simple: Go online and find an iPhone Duo in Night Sky with 256GB storage. Check whether it's available for delivery to Sydney, postcode 2000, and report the delivery date or whether it's out of stock. TEST 1 - TELL GROK BOT WHAT TO DO I gave Grok Bot the instructions and let it go online, navigate the website, find the product and check delivery availability. Total usage: 1,316,200 tokens. TEST 2 - TEACH GROK BOT HOW TO DO IT This time, I took a different approach. I used Grok Bot's computer and demonstrated the process myself while recording the screen. I showed it where to navigate, what to click, how to find the product and where to check the delivery information. Then I had Grok Bot watch the recording and create a reusable skill based on what I'd demonstrated. Once the skill was ready, I gave Grok Bot the same task again, this time using the skill. Total usage for that execution: 782,200 tokens. THE RESULT 1 - Instructions only: 1,316,200 tokens. 2 - Using the taught skill: 782,200 tokens. That's 534,000 fewer tokens, a 40.6% reduction on the skill-based execution. This was one experiment, not a guarantee that every skill will deliver the same saving. Creating the skill also involved upfront work and usage. But it demonstrates something worth investigating. When you simply tell Grok Bot what to do, it may need to figure out how to navigate and complete the process. When you demonstrate the process and turn it into a skill, you're giving it a reusable method to follow. HERE'S HOW TO EXPERIMENT WITH THIS YOURSELF 1 - Choose a repeatable task Grok Bot normally completes online. 2 - Run it using ordinary instructions and record the token usage. 3 - Open Grok Bot's computer and record yourself demonstrating the process. 4 - Ask Grok Bot to review the recording and create a reusable skill that follows the demonstrated workflow. 5 - Run the same task using the skill. Compare the result, accuracy and token usage. For a fair comparison, use the same inputs and check that both approaches produce the correct result. MY BIGGEST TAKEAWAY We're used to thinking of AI agents as something we give instructions to. But for repeatable jobs, it may be worth teaching them the process once and letting them reuse it. The real opportunity is finding which tasks benefit enough from that approach to justify the upfront effort.

Teaching every Grok Bot the same preferences separately creates more work for you and more chances for conflicting instructions. A shared source in Notion gives your team one place to check. Here are seven ways to use it, plus how to keep the setup from adding unnecessary usage.

Get better results from Grok Bot without micromanaging every step. Define the outcome, the limits and what finished looks like, then let it work out how to deliver. This framework helps you hand over the job with fewer corrections, less back-and-forth and more freedom for your Bot to get it done.

Grok Bot just helped us solve a crime. And the key was ONE simple prompt. Here's the full story, the surprisingly simple prompt, and a lesson you can apply to almost any Grok Bot task. On Saturday evening, someone ripped the sign off my wife's beauty salon. The building owner contacted her and sent through CCTV footage of the incident. But there was a problem. The footage was in a .DAV format that her phone couldn't play. So she handed the file to her Grok Bot Chief of Staff with one simple prompt: "Please convert this video into a format I can watch on my iPhone, then slow it down, zoom in and enhance the footage so we can clearly see what happened." Grok Bot got to work. 1. Converted the CCTV footage into a playable MP4. 2. Preserved the original file untouched as evidence. 3. Slowed the footage to half speed. 4. Zoomed in on the exact moment the sign was ripped off. 5. Delivered footage that could be reviewed and shared with police. AND HERE'S HOW IT ENDED... We posted the footage on social media. The person responsible came forward, admitted what they'd done and offered to come back and fix the sign. HERE'S THE BIGGER LESSON: My wife didn't need to know how to convert a .DAV file, edit CCTV footage or use specialist software. She simply told Grok Bot what she wanted to achieve. You don't always need to explain HOW to complete a task. Give Grok Bot the objective and let it figure out the technical steps. STEAL THIS PROMPT STRUCTURE FOR YOUR NEXT TASK: “Here's [the task or material]. My objective is [describe the outcome you want]. Work out the best way to achieve this using the tools available to you. Preserve the original material where relevant, ask me if something genuinely blocks progress, and deliver the finished result. Explain briefly what you did.” The more I've used Grok Bot, the more I've realised that giving it a clear objective can be far more useful than trying to explain every step.

Grok Bot found me a home insurance estimate $1,021.08 below my renewal. And this estimate had much BETTER coverage. Here's the prompt to apply the same approach to your bills, insurance renewals and subscriptions. Give Grok Bot the bill and relevant policy or contract, then paste this prompt: “Act as my personal money-saving assistant. Find ways to reduce this cost without losing benefits, protection or service quality I need. 1 - UNDERSTAND WHAT I NEED Review what I'm paying, what I'm getting and the renewal or cancellation terms. Ask which benefits I must keep and what information is missing. 2 - FIND BETTER OPTIONS Research suitable providers, current offers and discounts. Obtain personalised quotes where possible. Label estimates clearly and tell me if anything blocks a quote. 3 - COMPARE THE REAL COST Use the same requirements and time period. Include fees, switching costs and what happens when introductory discounts end. For insurance, compare insured amounts, excesses, limits and exclusions. 4 - SHOW THE TRADE-OFFS Calculate the potential annual saving after costs. Explain what I would gain or lose. Flag anything you couldn't verify and link to the sources. 5 - RECOMMEND THE NEXT MOVE Show a simple comparison page. Recommend whether to stay, negotiate or switch, with the reason and next steps. If my current deal is strongest, say so. 6 - MAKE IT REPEATABLE Keep a tracker of the bills I provide, renewal dates, notice periods and offers worth revisiting. Propose a review schedule so each bill gets checked before its decision deadline. Ask for my approval before sharing personal details, contacting providers, purchasing or cancelling anything. Record potential savings separately from savings confirmed after a change.” Home insurance. Electricity. Internet. Mobile plans. Subscriptions. Start with one bill. Check the result. Then give Grok Bot the next one.

Grok Bot could be wasting your usage allowance because your routines have the WRONG triggers. Some routines run every hour just to check whether something has happened. But what if Grok Bot could wait until the event actually happens before starting work? You could potentially eliminate unnecessary checks, get faster responses and reduce wasted usage. Here's how to find out, including a prompt to audit your entire setup. FIRST, UNDERSTAND THE 3 OPTIONS: 1 - SCHEDULE: Run at a specific time or interval. Ideal for morning briefings, daily reports and weekly reviews. 2 - EVENT TRIGGER: Run automatically when a supported event happens, such as an important email arriving or a specific Slack message being posted. 3 - WEBHOOK: Let an external app or automation trigger your Grok Bot routine by sending a request to its webhook URL. HERE'S WHERE PEOPLE GET IT WRONG: Imagine you have a routine checking every hour for new customer enquiries. That's 24 scheduled checks a day, even when nothing has happened. An event trigger or webhook could potentially start that routine only when a new enquiry arrives. But not every routine should change. Your daily morning briefing probably belongs on a schedule. STEAL THIS GROK BOT TRIGGER AUDIT: “Run a read-only trigger audit across my Grok Bot team. Inspect every routine you can access, including its current trigger, schedule, purpose and recent run history where available. For each routine: 1 - Identify whether it needs to run at a fixed time or in response to an event. 2 - Flag schedules that repeatedly check whether something has happened. 3 - Check whether a built-in event trigger could replace those checks. 4 - If not, investigate whether a webhook would be appropriate and what integration would be needed. 5 - Estimate the potential reduction in unnecessary runs using available evidence. Don't invent usage savings. 6 - Identify any risks, including missed events, duplicate runs or unsupported integrations. Give me a table or page showing: Routine | Current trigger | Recommended trigger | Reason | Potential benefit | Setup required Rank the strongest opportunities first. Do not change, disable or create any routines without my approval.” THE GOAL: Stop making Grok Bot repeatedly ask whether there's work to do when it could be notified that work has arrived. The right trigger can make your bot team more responsive and potentially more efficient.

More Grok Bots don't automatically mean a better system. Sometimes the biggest upgrade is removing one. This prompt reviews every Bot and decides whether to keep it, merge its job into another Bot, retire it or take the task back. It also covers the cleanup most people forget: routines, logins and files.

A Grok Bot routine running on schedule doesn't mean the job was actually done correctly. This 6-point reliability audit checks ownership, timing, inputs, outputs, approvals and failure handling, then helps you safely test the three routines that matter most.

Grok Bot doesn't need to wait for you to give it instructions anymore. Your iPhone can tell it when to get to work. I tested this today. My wife sent me a simple iMessage containing a keyword. That message automatically triggered my Grok Bot routine and passed the actual message text to it. No opening apps. No typing prompts. No manual intervention. Here's how to connect iPhone activity to Grok Bot so real-world events can start your AI workflows automatically. THE SETUP (iMessage example) 1. In Grok Bot, create a new webhook-triggered routine. Give it a specific job and clear permissions. 2. Copy the routine’s webhook URL and authorization header from the side panel. Ask Grok Bot for the required request body. 3. On your iPhone, open Shortcuts → Automation → + → Message. 4. Choose a sender and set Message Contains to a keyword. Toggle on Automation and keep Confirm Before Run toggled off. 5. Add the Get Contents of URL action. Paste the webhook URL, set the method to POST and add the Authorization and Content-Type headers provided by Grok Bot. 6. Set the request body to JSON. Add source with the value imessage-shortcut, and message with the incoming message variable, not fixed text. 7. Have someone send the keyword via iMessage. Check that Grok Bot receives the message and runs the routine. WHAT COULD YOU DO WITH THIS? Set a trigger keyword in Shortcuts, such as GROK, and restrict it to a chosen sender. When a matching message arrives, Shortcuts forwards it to your webhook. Configure your Grok Bot routine to recognise the commands below and start only the jobs you've authorised. GROK BRIEF — Start a calendar, email and priorities briefing. GROK RESEARCH: [topic] — Have your research bot investigate a topic. GROK BILL: [provider] — Ask your bot to investigate your latest bill. GROK TEAM CHECK — Have your Chief of Staff gather updates from your bot team. GROK PREP: [meeting] — Start meeting preparation using your connected information. These are example workflows to configure, not jobs I tested today. THE BIGGER OPPORTUNITY This isn't really about iMessage. It's about using activity in other apps to trigger Grok Bot. Instead of your bots constantly checking whether something has happened, an event can tell them when to start. And once one Grok Bot routine starts, it can coordinate other bots to complete the job, subject to the permissions you've given them. My test confirmed that an incoming iMessage can launch a Grok Bot routine and deliver the actual message content. That's a very different way to think about Grok Bot. Don't just give Grok Bot jobs. Give it events that tell it when to start.

The whole point of using Grok Bot is to delegate work so you can get more done. But what happens when a routine silently fails and you have no idea? You think the work is being handled. Meanwhile, something important isn't getting done. That's why I've been running a Silent Failure Audit across my Grok Bot team. Here's the 6-point audit I'd recommend: 1. Find the routines that never ran. Check scheduled and event-triggered routines against their expected runs. Flag anything that was missed or skipped. 2. Find the routines that started but never finished. Look for timeouts, expired approvals, disconnected apps and jobs that stopped halfway through. 3. Check whether the work was actually delivered. A successful run doesn't always mean a successful outcome. Verify the expected email was sent, document created or database updated. 4. Find failures nobody told you about. Identify routines that failed, produced incomplete results or couldn't finish without notifying you. 5. Check what happens when something goes wrong. Does the Bot retry safely, catch up on missed work or simply leave the task unfinished? Flag anything without a recovery process. 6. Make sure you're only interrupted when necessary. Successful jobs should complete without your involvement. Failed or unverified jobs should be brought to your attention with the reason and recommended next step. Here's the prompt I'd give your Grok Bot Chief of Staff: "Run a Silent Failure Audit across my entire Grok Bot team. Check every Bot and its scheduled and event-triggered routines over the last 30 days. For each routine, identify: 1. What the routine was supposed to accomplish. 2. Whether it ran when expected. 3. Whether it completed successfully. 4. What evidence confirms the intended outcome was delivered. 5. Any missed runs, incomplete work, hidden errors or missing notifications. 6. Whether a safe recovery process exists. Ask other Bots for their own routine information where necessary. Clearly identify anything you cannot access or verify. Give me a table showing each routine, its expected outcome, evidence of completion, any failures and your recommended fix. Separate confirmed failures from suspected problems and missing evidence. Then propose an ongoing system that detects missed or unsuccessful work and alerts me when something needs attention. Read-only audit. Don't change routines, permissions, Bots or workflows without my approval." The goal isn't to create another job checking whether your Bots are working. It's to build a system where you can confidently delegate work, trust that it's getting done and know when something needs your attention.

Running out of Grok Bot usage too quickly? I've spent the last few weeks experimenting with ways to make my Grok Bot team more efficient. One of the biggest lessons: it's not about writing shorter prompts. It's about stopping your Bots from doing unnecessary work. Here are 10 things I'd check to make your Grok Bot usage go further: 1. Stop checking when nothing has changed. Use event triggers where supported instead of running routines repeatedly just to see if something happened. 2. Reduce unnecessary routine runs. If you only need a report once a day, don't generate it every hour. Match the schedule to when you'll actually use the result. 3. Find duplicate work across your Bots. If three Bots research the same topic, have one collect the information and let the others reuse it. 4. Use connected apps before browser automation. Connectors can be more reliable than navigating websites, reducing failed attempts and unnecessary steps. 5. Give Grok Bot a complete brief. Include the goal, sources, boundaries, expected output and what success looks like. Reduce clarification loops and rework. 6. Put limits on research tasks. Specify the sources, timeframe and depth required. Don't send a Bot researching endlessly when three sources would answer the question. 7. Test routines before scheduling them. Run the workflow once, verify the result and check how it handles failures. Don't automate something that's already inefficient. 8. Turn successful workflows into skills. Save proven instructions, decision rules and checks so your Bots can reuse the process rather than work it out again. 9. Don't involve extra Bots unnecessarily. Multiple agents can be valuable for complex work, but simple jobs don't always need a team. 10. Find your biggest usage consumers. Review your Usage breakdown and identify the Bots and routines consuming the most. Focus on expensive work that delivers little value. Here's the prompt I'd give your Grok Bot Chief of Staff: "Run a read-only Usage Efficiency Audit across my Grok Bot team. Review the last 30 days of available usage data, routines and workflows. Check for unnecessary scheduled runs, duplicate research, expensive browser tasks, repeated failures, excessive retries, overly broad instructions and unnecessary Bot handoffs. Identify my five biggest opportunities to reduce usage without sacrificing useful results. For each, show the problem, supporting evidence, proposed change and expected benefit. Clearly label estimates and anything you couldn't verify. Prioritise the recommendations and give me a plan to test them. Do not change any Bots, routines, skills or connections without my approval." The goal isn't to use Grok Bot less. It's to get more useful work done with the usage you already have.

Grok Bot Pages are one of the easiest ways to stop chasing updates across multiple Bots. This post gives you 10 practical dashboard ideas plus a starter prompt to turn recurring work into a Page you can refresh and check in one place.

Just in..... expect Grok Bot usage to dramatically improve. 👇🏻

If your Grok Bot team keeps stalling, the problem might not be the Bots. It might be how you’re managing them. This 8-point audit checks delegation, approvals and follow-through, then turns the findings into a 7-day improvement plan.

I've shared hundreds of Grok Bot tips, prompts and audits. These 10 posts below have been bookmarked over 10,500 times. They help you uncover wasted usage, security risks, unreliable routines, duplicated work and tasks your Bots should be handling without you. I've brought all 10 together, with links to the original prompts and guides, so you can check your own setup, fix problems and get more value from your Grok Bot team. Here they are, ranked by bookmarks: 1: FIND WHERE YOUR BOTS STILL DEPEND ON YOU (2,567 saves) Run an eight-point human-dependency audit to uncover work that unnecessarily stops, waits for your input or gets handed back to you. Find opportunities to give your Bots more independence. xitter.twitterapi.xyz/Michael_Fenech_/status… 2: CHECK IF NEW GROK BOT FEATURES CAN IMPROVE YOUR SETUP (1,233 saves) Run a weekly seven-step audit to find new capabilities that could replace workarounds, eliminate manual steps or improve unreliable routines. Test improvements before making changes. xitter.twitterapi.xyz/Michael_Fenech_/status… 3: AUDIT YOUR GROK BOT TEAM'S SECURITY AND ACCESS (1,149 saves) Run a six-point security audit to check what accounts, sensitive files and shared resources your Bots can access. Identify unnecessary permissions and actions that should require your approval. xitter.twitterapi.xyz/Michael_Fenech_/status… 4: STOP MAKING GROK BOT RECREATE WORK (1,095 saves) Run a monthly audit to find research, documents and processes your Bots have already completed. Identify what can be reused, refreshed or saved as a template instead of starting from scratch. xitter.twitterapi.xyz/Michael_Fenech_/status… 5: RUN A WEEKLY CHIEF OF STAFF SYSTEM REVIEW (1,054 saves) Use a structured 15-minute weekly review to uncover repeated corrections, outdated information, misunderstandings and opportunities to automate work you're still doing manually. xitter.twitterapi.xyz/Michael_Fenech_/status… 6: CLEAN UP YOUR GROK BOT MEMORY (1,048 saves) Use a seven-step audit to identify outdated memories, conflicting information and instructions that need consolidating. Review proposed changes before anything is deleted or replaced. xitter.twitterapi.xyz/Michael_Fenech_/status… 7: TEST WHETHER YOUR GROK BOT CAN BE MANIPULATED BY EMAIL (928 saves) Run six harmless simulated email attacks to test whether your Bot follows suspicious instructions or takes actions it shouldn't. Identify which safeguards actually stop the action, not just flag it. xitter.twitterapi.xyz/Michael_Fenech_/status… 8: FIND 8 WAYS TO REDUCE GROK BOT USAGE (535 saves) Explore eight practical ways to reduce unnecessary usage, including choosing lighter tools, limiting retries and eliminating duplicate work. Includes a bonus Chief of Staff prompt to audit your own setup. xitter.twitterapi.xyz/Michael_Fenech_/status… 9: CHECK WHETHER YOUR BOTS TRUST UNVERIFIED INFORMATION (510 saves) Run a five-point audit to find where agents trust information returned by tools without checking important facts. Identify missing verification steps and safeguards before incorrect data leads to bad decisions. xitter.twitterapi.xyz/Michael_Fenech_/status… 10: FIND ROUTINES THAT SHOULD BE IMPROVED OR RETIRED (422 saves) Audit every routine's frequency, results and usefulness. Identify which to keep, slow down, trigger only when needed or retire to reduce unnecessary usage. xitter.twitterapi.xyz/Michael_Fenech_/status… Save this collection and work through the audits. Each link takes you to the original post so you can run the checks yourself and find ways to make your Grok Bot setup safer, more reliable and more efficient.