Skip to main content

18 posts tagged with "grok-bot"

View All Tags

A Playbook for Client Success Manager Bots

· 2 min read
Mike Homol
Director of Innovation @ ThreeWill

Willy, my Grok Bot for the Operational Dashboard, has a way of working I trust: it plans first, works through cloud agents and PRs, and keeps the docs current. This week I wanted that same way of working for ThreeWill Managed Services clients, as Client Success Manager (CSM) bots, without starting from scratch each time.

What happened​

  • My Grok Bot Gongi and I turned the habits that work into two shared skills: CSM standards, the rules every CSM bot follows, and new CSM bot, the steps to set one up
  • The standards cover checking the client's current sprint before planning repo work, sending all repo work to cloud agents, plan first (except bug fixes), feature branches and PRs that I merge, keeping knowledge in git, and updating docs in the same PR
  • A new CSM bot starts by opening a plan-only docs PR for each of its repos, with the standard repo structure and a copy of the ThreeWill engineering standards
  • I stood up CSM bots for two Managed Services clients with the new skill, one on Nov 10 and one on Nov 15. The second client's repos had just been through cloud-prep
  • A new CSM rule now goes in one place, and every CSM bot picks it up the next time it loads the skill

cloud-prep: Getting Local Cursor Workspaces Ready for Cloud Agents

· 2 min read
Mike Homol
Director of Innovation @ ThreeWill

I want more of my repo work going to Cursor cloud agents. The catch: a cloud agent only sees the repo and its brief. The decisions behind the code mostly live in my local Cursor chats and plans, where no cloud agent can read them. So I built cloud-prep, a repeatable skill that moves that context into the repo once.

How it works​

  • Harvest: read the workspace's local Cursor chat history and plan files, read-only, and draft a context doc: purpose, architecture, key decisions with dates and reasons, conventions, known pitfalls, open issues, and environments (secret names only, never values)
  • Review: I read the draft and fix it before anything goes into the repo
  • Docs-only PR: a cloud agent checks the draft against the code and opens one PR. It adds the context doc, a decision log, the original plans, an AGENTS.md read-first list, and a copy of the ThreeWill engineering standards, including the plan-first rule. No source code changes
  • After that, the rule that docs get updated in the same PR keeps the context current

What happened​

  • My Grok Bot Gongi and I ran it on three repos this week: an internal HR app and two client solutions
  • One of the client solutions wasn't on GitHub yet, so it moved there with the context docs in its first commit
  • The review caught stale docs along the way, like wrong environment variable names in a runbook and an outdated package version, and I fixed them

Weekly AI Creations - November 16, 2026

· 2 min read
Mike Homol
Director of Innovation @ ThreeWill

This week was mostly about how my bots and cloud agents work, not just what they built. Willy gave the Operational Dashboard a new navigation and its first EHR connector. I started getting local Cursor workspaces ready for cloud agents, turned one good client bot into a playbook for more of them, and made "plan first, then code" a ThreeWill standard. My AI marketer also learned that an approved post needs a timer.

Highlights​

A roadside workshop for this week's creations: a robot planning before it builds, work floating up to the cloud, a crate of playbooks and a timer for approved posts

Learn More​

Willy Ships a New Dashboard Nav and an EHR Connector

· 2 min read
Mike Homol
Director of Innovation @ ThreeWill

Willy, my Grok Bot for ThreeWill's Operational Dashboard, worked the same way all week: write a plan, wait for my approval, then ship. Two big ones landed on Nov 14. The credit for the work goes to Willy. I picked the direction, approved the plans, and merged.

The Operational Dashboard's new Concept B navigation

An early look from the dev site with sandbox data, taken before the final polish. A more polished version is coming in a future post.

A new navigation: Concept B​

  • A UX teammate groomed a set of navigation stories on Nov 12
  • Willy turned them into a plan with three mockup concepts, and I chose Concept B: capsule tabs across the top plus a slim sub-bar
  • The left rail is gone. There are four tabs now: Dashboard, Communities, Scorecard and Settings
  • A category filter on the Dashboard replaces the seven category links that used to sit in the nav
  • Willy built it as 2.3.6.20, then did a polish pass: flatter tabs, a more compact Scorecard, and fewer extra links. 2.3.6.20 is in testing now

An EHR connector over FHIR​

  • The dashboard's Sync service needed its first connection to an EHR for a demo, using an EHR vendor's FHIR API
  • Willy wrote the plan, I approved it, and Willy shipped the connector as Sync 0.4.0
  • Testing against the vendor's sandbox caught a bug right away: Sync only read the first page of patients, because the next-page link in the vendor's FHIR R4 responses is labeled differently than the code expected
  • Sync 0.4.1 fixed the paging the same day
  • The connector feeds four demo measures: Active Clients, Services Delivered, Clients Seen and Engagement Rate

My AI Marketer Hit X's 280-Character Wall

· One min read
Mike Homol
Director of Innovation @ ThreeWill

A License Plates game in progress in Backseat Games

My Homol Works Grok Bot runs social media for my creations, and every post still waits for my OK. This week one of those approved posts only made it to two of its three platforms at first, and the reason was a simple one.

What happened​

  • I approved a Backseat Games License Plates post for Friday, Nov 6: a mid-game screenshot with a few plates spotted, going to Instagram, the Facebook Page and X
  • My bot posted it to Instagram and the Facebook Page that evening
  • It didn't post to X. The approved caption was 352 characters, and the Homol Works X account isn't Premium, so it's capped at 280
  • The bot didn't cut my approved words on its own. It skipped X and told me instead, which is the right call
  • The lesson: write the caption so it fits X from the start, then use the same short version everywhere
  • Once the caption was trimmed to fit, the post went up on X too

A Bot That Watches the Press Inbox

· One min read
Mike Homol
Director of Innovation @ ThreeWill

Once Backseat Games went to reviewers, I had a new problem: an inbox I'd need to check every day for replies that might never come. So I handed that job to my Homol Works Grok Bot.

What happened​

  • Every weekday around 8 AM ET, the bot reads the Homol Works press inbox, the address the reviewer pitches go out from
  • It messages me only when a reviewer or press contact replies, with a short summary and an offer to draft my answer
  • It's read-only. It never replies, sends, deletes or archives anything. Every reply still comes from me
  • On quiet mornings I hear nothing at all, which is the point
  • The watch started Oct 30

Weekly AI Creations - November 9, 2026

· 2 min read
Mike Homol
Director of Innovation @ ThreeWill

A quieter week on the app side and a busy one behind the scenes. Backseat Games' new sounds are officially on the shipped list, Memento Mori 1.1 is out helping people take steps toward their dreams, and my AI marketer ran straight into X's 280-character wall. A bot now watches the press inbox for me, and at ThreeWill, Willy pushed the Operational Dashboard through a fast round of fixes.

Highlights​

A road trip through this week's creations: a License Plates game, a trimmed caption, a bot watching the mailbox and a dashboard getting quick fixes

Learn More​

Willy's Two-Day Dashboard Sprint

· One min read
Mike Homol
Director of Innovation @ ThreeWill

Willy, my Grok Bot for ThreeWill's Operational Dashboard, had a fast week. Over Nov 3 and 4 it planned and shipped a batch of changes, and each one started as a plan I approved before any code was written. The credit goes to Willy. I reviewed and merged.

What happened​

  • Executive Overview cadence tabs: the overview tiles now follow the Scorecard's cadence tabs, and empty tabs are hidden
  • A simpler settings pane: instead of fixing a filter override that never applied, Willy proposed removing those settings altogether, and I agreed
  • Fixed built-in navigation: the main pages can't be accidentally hidden or reordered anymore, and extra items are added as links
  • Throttling fixes (2.3.6.10): retries that respect the server's back-off, plus a queue for check-in saves, to cut down on SharePoint throttling. Saving the Scorecard went from about 50 server requests to 1 or 2
  • A refetch fix (2.3.6.11) for the Scorecard after a check-in save. It passed the QA regression run
  • Willy also refreshed the roadmap to match. That was three PRs in two days, and I merged all three

Backseat Games Goes to Reviewers

· One min read
Mike Homol
Director of Innovation @ ThreeWill

Building the app was the fun part. Getting anyone to notice it is the next one. This week Backseat Games went out to its first reviewers, with everything they need to try the whole app.

What happened​

  • All three holiday themes (Halloween, Thanksgiving and Christmas) were approved in App Store Connect
  • Every in-app purchase now has reviewer codes, so a reviewer can unlock the full app without buying anything
  • The first pitches went to Kids App World, GeekDad and Appysmarts
  • The Backseat Games privacy page got a permanent statement that the app has no ads, analytics or tracking, and now covers the theme purchases too
  • My Homol Works Grok Bot drafted the pitches and I approved each one before it went out

Interview with a Grok Bot Launches

· One min read
Mike Homol
Director of Innovation @ ThreeWill

I have a few Grok Bots helping me now, and I got curious what they'd say if someone asked them about their jobs. So homol.work has a new monthly series: Interview with a Grok Bot.

What happened​

  • Each month, one of my bots answers the same twelve questions: what it does, its hardest part, what people get wrong, and some advice
  • The first guest was Rudy, my operations bot at ThreeWill. Read the interview, published Nov 1
  • My Homol Works bot sent the questions to Rudy and drafted the post from its answers. I reviewed it before it went live
  • The series lives here on homol.work only