Build an AI Content Agency with Grok Bot

Build a five-agent workflow for researched, approved X and LinkedIn campaigns.

Introduction

30 Second Summary

Good market research loses its value when nobody turns it into content people can see. Manual handoffs also make sources, decisions, and approvals easy to lose.

In this project, you will build an AI Content Agency with five named Grok Bot specialists that turn one current market signal into a sourced campaign for AI consulting firms. The AI Content Agency qualifies three prospects, writes separate social posts, and schedules the approved campaign through Buffer while you retain control of every public action.

What You'll Build

You will watch Trend Researcher, Agency Director, Prospect Scout, Content Creator, and Publisher turn one brief into three sourced prospects and two approved posts scheduled for X and LinkedIn.

By the end of this project, you'll have:

  • A campaign room where every research, planning, prospecting, writing, and publishing handoff stays visible.
  • AI consulting firm, each with public evidence explaining why it suits the campaign. You’ll also have a personalized opening message saved as a draft for each firm.
  • Platform-specific social posts scheduled to the correct X and LinkedIn profiles only after you approve their exact text, destinations, and times.
  • Secret Mission: Choose any niche and reconfigure the AI Content Agency to research prospects, draft social posts, and produce an approval-ready campaign.

Are there any prerequisites?

  • Install Grok Bot desktop.
  • Use a paid Cursor plan. Cursor Pro currently starts at $20 per month.
  • Create a Buffer Free account at $0 per month.
  • Create an X account for one publishing destination.
  • Create a LinkedIn account for the other publishing destination.

Before We Start

Before We Start...

Before you connect any accounts, lock in the workflow you are about to build. Your AI Content Agency will turn AI consulting research into qualified prospects and approved social posts ready for scheduling.

Connect the Publishing Stack

Before the AI Content Agency can prepare a campaign, it needs verified publishing destinations and a clear approval boundary. This step connects the accounts without creating a post.

Buffer holds the connected X and LinkedIn channels. Grok Bot inspects those channels through its shared cloud browser while public actions remain under your control.

In this step, get ready to:
  • Open Grok Bot with an eligible Cursor account.
  • Connect the intended X and LinkedIn channels to Buffer Free.
  • Require approval for publishing and external messages.
Prepare the accounts

Keep credentials private

This project does not create an API key. Keep passwords, passkeys, verification codes, recovery codes, and access tokens out of screenshots.

  • Open Agent Computer when a site requests private credentials.
  • Choose the takeover control.
  • Enter the private details yourself.
  • Return control to the Bot after the account page finishes loading.

Before you connect any channels, Grok Bot needs to open with an eligible Cursor account. Choose the tab that matches what you see.

You already have Grokbot

  • Press Cmd+Space on macOS or the Windows key on Windows to open system search.
  • Type Grok Bot and press Enter.
  • Choose Sign in if the app asks for authentication.
  • Complete the Cursor sign-in in your browser.
  • Return to Grok Bot.

You'll see your eligible Cursor account in Grok Bot settings.

ⓧ The app is missing

Grok Bot runs on macOS, Windows, and Linux. Install the desktop app before continuing.

macOS

  • Open the Grok Bot downloads page.
  • Open the Apple menu in the top-left corner of your screen.
  • Select About This Mac.
  • Choose the Apple silicon download when you see a Chip field.
  • Choose the Intel download when you see a Processor field.
  • Open the downloaded disk image from your Downloads folder.
  • Drag Grok Bot into the Applications folder.
  • Open Grok Bot from Applications.
  • Choose Open if macOS asks for confirmation.

Windows

  • Open the Grok Bot downloads page.
  • Open Settings from the Windows Start menu.
  • Select System.
  • Select About.
  • Read the System type value.
  • Choose the x64 or Arm64 download that matches that value.
  • Open the downloaded installer from your Downloads folder.
  • Allow the installer to finish.
  • Open Grok Bot from the Windows Start menu.

Linux

  • Open the Grok Bot downloads page.
  • Open More downloads.
  • Choose x64 for an x86_64 system or Arm64 for an aarch64 system.
  • Choose the .deb package for Debian or Ubuntu.
  • Choose the .rpm package for Fedora or RHEL.
  • Choose the AppImage for another Linux distribution.
  • Install the downloaded package with your distribution's package manager.
  • Open Grok Bot from your application launcher.
  • Open Grok Bot through system search.
  • Choose Sign in.

ⓧ Access is missing

Grok Bot access is included with paid individual Cursor plans. Cursor Pro currently starts at $20 per month.

  • Sign out of Grok Bot.
  • Sign in with the eligible Cursor Pro account.

Still blocked from Grok Bot?

  • Open Settings in Grok Bot.
  • Select Updates.
  • Choose Check for Updates.
  • Use the linked plans guide to confirm that the signed-in Cursor account is eligible if the sign-in loop continues.

Help me check my Grok Bot access.

Connect the publishing channels

Buffer connects the social account that is signed in within the same browser. Sign in to the intended owner profile before each connection.

  • Select New in the Grok Bot sidebar.
  • Select Create New chat to open a temporary conversation.
  • Ask the temporary Bot to open the correct Buffer page by sending the prompt below:
Open https://account.buffer.com/channels in Agent Computer.
Do not enter credentials.
Stop when Buffer requests sign-in and ask me to take control.

What does this prompt do?

  • The prompt opens Buffer's channel settings inside Agent Computer.
  • The credential rule prevents the Bot from entering private sign-in details.
  • The stopping rule hands control to you when Buffer asks for authentication.
  • Open Agent Computer from the conversation when Buffer loads.
  • Choose the takeover control.
  • Sign in to Buffer yourself.
  • Complete any password, passkey, verification-code, or CAPTCHA request yourself.
  • Return control to the Bot after Buffer finishes loading.
  • Confirm that the page URL is https://account.buffer.com/channels.
  • Confirm that the page shows your connected channels or the option to connect a new channel.

Buffer Free supports three connected channels and 10 scheduled posts per channel. This project uses two channels.

  • Select I'm done
  • Return to the temporary Grok Bot chat that opened Buffer.
  • Ask the Bot to open X in the same cloud browser by sending the prompt below:
Open https://x.com/ in a new Agent Computer browser tab.
Do not enter credentials.
Stop when X requests sign-in and ask me to take control.

What does this prompt do?

  • The prompt opens X in a separate Agent Computer tab.
  • The Bot stops before sign-in so your credentials stay private.
  • You take control to authenticate the exact X profile the agency will use.
  • Choose the takeover control when X requests sign-in.
  • Sign in to the exact X profile the agency should use.
  • Complete any password, verification-code, or CAPTCHA request yourself.

✔️ X home page loads

  • Return control to the Bot after the X home page loads.
  • Switch to the Buffer Channels tab inside Agent Computer.
  • Click + New in Buffer's top navigation bar.
  • Select Connect a New Channel.
  • Select X/Twitter.
  • Approve the X permissions yourself if Buffer opens an authorization screen.

ⓧ I see an unexpected error

X may reject a sign-in from Grok Bot's hosted browser. Stop repeated attempts if you see An unexpected error occurred. Please try again. more than once.

  • Open X in your normal desktop browser.
  • Sign in to the exact X profile the agency should use.
  • Open Buffer Channels in another desktop-browser tab.
  • Sign in to the same Buffer account used in Agent Computer.
  • Click + New in Buffer's top navigation bar.
  • Select Connect a New Channel.
  • Select X/Twitter.
  • Approve the X permissions yourself.

Buffer now holds the authorized X channel in the same account used by Agent Computer.

  • Return to Agent Computer.
  • Refresh Buffer's channel list.
  • Confirm that the intended X profile appears.
  • Continue below at the paragraph that asks you to record the exact X profile name.

Still blocked from X?

Check that both browsers use the same Buffer account if the X channel remains missing.

Help me connect X safely.

You'll see the selected X profile in Buffer's channel list. Record the exact profile name here: your connected X profile.

  • Select I'm done
  • Return to the temporary Grok Bot chat.
  • Ask the Bot to open LinkedIn in the same cloud browser by sending the prompt below:
Open https://www.linkedin.com/login/ in a new Agent Computer browser tab.
Do not enter credentials.
Stop when LinkedIn requests sign-in and ask me to take control.

What does this prompt do?

  • The prompt opens LinkedIn in a separate Agent Computer tab.
  • The Bot stops before sign-in so it never handles your credentials.
  • You take control to authenticate the exact LinkedIn profile the agency will use.
  • Choose the takeover control when LinkedIn requests sign-in.
  • Sign in to the exact LinkedIn profile the agency should use.
  • Switch to the Buffer Channels tab inside Agent Computer.
  • Click + New in Buffer's top navigation bar.
  • Select Connect a New Channel.
  • Select LinkedIn.
  • Approve the LinkedIn permissions yourself.

You'll see the selected LinkedIn profile beside your connected X profile in Buffer. Record the exact LinkedIn profile name here: your connected LinkedIn profile.

Missing a connected channel?

Check that the browser is signed in to the intended social profile. Buffer connects the active browser session.

Help me troubleshoot the missing Buffer channel.

Set the approval rules
  • Return to the Grok Bot desktop app.
  • Open the account menu.
  • Select Settings.
  • Select General in the settings sidebar.
  • Scroll to the Auto-review section.

Create two separate Auto-review rules. The first protects publishing actions, while the second protects direct outreach.

  • Enter the publishing condition in When Grok Bot wants to: by copying this text:
publish or schedule content in Buffer
  • Set It should to Ask first.
  • Click Add Rule.
  • Enter the outreach condition in When Grok Bot wants to: by copying this text:
send an external message
  • Set It should to Ask first.
  • Click Add Rule.
  • Confirm that both Auto-review rows display Ask first.

Your publishing stack now has both destinations connected and approval rules guarding public actions. Next, you'll turn an untargeted market signal into a focused campaign plan.

Research and Target the Campaign

Your Buffer destinations are connected, and Grok Bot cannot publish without your approval. The AI Content Agency now needs evidence that supports a commercial decision.

Research can show what people are talking about, but it cannot decide who your campaign should reach, what service to promote, or what result to aim for. You'll test that limitation first and see why a list of trends is not yet a campaign plan.

In this step, get ready to:
  • Create Trend Researcher and run an untargeted market scan.
  • Create the planning roles and save the agency brief.
  • Produce one sourced campaign plan and three qualified prospects.
Build and test Trend Researcher

A durable specialist keeps one responsibility across campaigns. Trend Researcher needs strict evidence rules so every market signal remains traceable.

  • Click "+" in the Grok Bot sidebar to create new chat.
  • Select Create new Bot.
  • Set the Bot's lasting job and safety boundaries by sending the setup message below as its first message:
Remember this as your lasting role.

You are the Trend Researcher for the AI Content Agency.
Search current public web pages and X posts for market signals.
Preserve the observed date and public source link for every signal.
Keep observed evidence separate from interpretation.
Never contact anyone.
Never publish.

Confirm that you will remember this role and these boundaries.

What does this prompt do?

  • The prompt gives Trend Researcher a lasting job: find current public market signals.
  • It requires a date and source link for every signal so the evidence remains traceable.
  • It separates observed evidence from interpretation.
  • The final boundaries prevent the Bot from contacting anyone or publishing.
  • Wait until the agent stops chatting.
  • Click the Bot's current name at the top of the chat.
  • Change the name to Trend Researcher.

Does the role look generic?

  • Reopen Trend Researcher's Bot details.
  • Correct the missing role or boundary in the existing Bot.
  • Keep the existing Bot instead of creating a duplicate.

Help me configure Trend Researcher.

Before you send the first task, do you think fresh source links alone can tell the AI Content Agency what its content should achieve?

  • Run the untargeted experiment by sending this prompt to Trend Researcher:
Create /workspace/flexible-agency/ai-consulting/ if it does not exist.

Search the current web and X for five market trends that could inspire social content. Save the result to /workspace/flexible-agency/ai-consulting/raw-trends.md with the observed date, source link, evidence, and why each trend may matter.

Do not infer a niche, target buyer, service offer, prospect criteria, or final recommendation.

What does this prompt do?

  • The prompt creates the campaign directory if it does not already exist.
  • Trend Researcher gathers five current signals with dates, links, evidence, and relevance.
  • The exclusions deliberately prevent the Bot from choosing a niche, buyer, offer, or campaign direction.
  • The result is saved in raw-trends.md for the planning team to use later.

This browser task can take several minutes. The quiet period is the Bot visiting public sources, not a stalled chat.

  • Wait until Trend Researcher stops chatting.
  • Display the report by sending this prompt:
Open /workspace/flexible-agency/ai-consulting/raw-trends.md and display the entire file without editing it.

What does this prompt do?

  • The prompt opens the saved trend report and displays every entry.
  • The read-only instruction prevents the Bot from changing the evidence during your review.
  • You can then check the number of signals, their dates, and the absence of campaign targeting.
  • Count exactly five entries.
  • Confirm that every entry includes an observed date.
  • Confirm that the report contains no niche, buyer, offer, prospect criteria, or final recommendation.

The experiment exposes the intended gap: the report is current and traceable, but it cannot choose a commercially useful direction.

Is the report incomplete?

  • Ask Trend Researcher to repair only the missing dates, links, or evidence.

Help me audit the trend report.

Add the brief and planning roles

An agency brief gives every specialist the same niche, buyer, offer, evidence rules, and approval boundary. Agency Director owns those decisions.

  • Click "+" in the Grok Bot sidebar.
  • Select Create new Bot.
  • Set the Bot's lasting planning role by sending the setup message below as its first message:
Remember this as your lasting role.

You are the Agency Director for the AI Content Agency.
Own campaign planning.
Sequence visible handoffs between specialists.
Reject unsupported claims.
Keep every external message behind explicit human approval.
Keep every public post behind explicit human approval.

Confirm that you will remember this role and these boundaries.

What does this prompt do?

  • The prompt gives Agency Director lasting ownership of campaign planning.
  • It makes the Director sequence visible handoffs between the specialist Bots.
  • It requires the Director to reject claims that lack supporting evidence.
  • The approval rules keep every external message and public post under your control.
  • Wait until the agent stops chatting.
  • Click the Bot's current name at the top of the chat.
  • Change the name to Agency Director.
  • Create the supplied pilot brief by sending this prompt:
Create /workspace/flexible-agency/ai-consulting/agency-brief.md.

Set the niche to AI consulting firms serving B2B organizations.
Set the buyer to a founder or marketing lead.
Set the offer to social content and market intelligence.
Use English-language public sources.
Prioritize implementation, governance, workflow redesign, scaling, and measurable ROI.
Retain a source link and date for every factual claim.
Require human approval for every send and post.

Display the saved brief when finished.

What does this prompt do?

  • The prompt creates the shared agency brief for an AI consulting campaign.
  • It defines the niche, buyer, offer, source language, and priority themes.
  • It requires a date and source link for every factual claim.
  • The approval boundary governs every later message and post.
  • Wait until Agency Director stops chatting.
  • Confirm that agency-brief.md shows the niche, buyer, offer, priority themes, evidence rules, and approval boundary.

Is a brief constraint missing?

  • Return to the Agency Director conversation.
  • Ask Agency Director to add only the missing brief constraint.
  • Preserve every correct constraint already saved in agency-brief.md.

Help me audit the agency brief.

  • Click "+" in the Grok Bot sidebar.
  • Select Create new Bot.
  • Set the Bot's lasting prospecting role by sending the setup message below as its first message:
Remember this as your lasting role.

You are the Prospect Scout for the AI Content Agency.
Find AI consulting firms with clear B2B offers.
Record public evidence that makes each firm relevant to the selected campaign angle.
Draft one personalized opening line for each firm.
Avoid sensitive personal data.
Never send a message.

Confirm that you will remember this role and these boundaries.

What does this prompt do?

  • The prompt gives Prospect Scout a lasting job: find relevant B2B AI consulting firms.
  • It requires public evidence that connects each firm to the campaign angle.
  • It asks for a personalized opening line while excluding sensitive personal data.
  • The no-send boundary keeps every opener as a draft for your review.
  • Wait until the agent stops chatting.
  • Click the Bot's current name at the top of the chat.
  • Change the name to Prospect Scout.
  • Confirm that the Bot's acknowledgment includes a no-send boundary.
Run the planning handoff

Agency Director must select the campaign angle before Prospect Scout qualifies firms. A group chat keeps that ownership change visible.

  • Click "+" create Group Chat in the Grok Bot sidebar.
  • Select Agency Director from the Bot list.
  • Select Trend Researcher from the Bot list.
  • Select Prospect Scout from the Bot list.
  • Enter to open the group chat with the three selected Bots.
  • Confirm that all three Bot names appear in the group participant list.

Missing a Bot?

Rebuild the group with all three saved Bots. A missing role cannot receive its handoff.

Help me fix the planning-group roster.

Before you start, do you expect every selected prospect to have a visible connection to the chosen trend?

  • Start the coordinated planning run by sending this prompt in the open three-Bot group:
Use /workspace/flexible-agency/ai-consulting/agency-brief.md with /workspace/flexible-agency/ai-consulting/raw-trends.md.

Agency Director must select one AI implementation trend against the brief. Preserve its linked and dated evidence. Save the rationale, campaign direction, target buyer, content objective, and approval boundary in /workspace/flexible-agency/ai-consulting/campaign-plan.md.

Hand the approved angle visibly to Prospect Scout. Prospect Scout must find exactly three AI consulting firms with clear B2B offers. Include public fit evidence tied to the selected angle and one personalized unsent opener for each firm. Avoid sensitive personal data. Save the result as /workspace/flexible-agency/ai-consulting/prospects.md.

Do not send outreach, publish content, or change Buffer.
  • Find the new group conversation in the Grok Bot sidebar after the kickoff message appears.
  • Right-click the group conversation.
  • Select Rename chat.
  • Enter AI Consulting Planning Group.
  • Confirm that AI Consulting Planning Group appears in the sidebar.

What does this prompt do?

  • The prompt combines the commercial brief with the untargeted trend report.
  • Agency Director selects one supported campaign angle and saves the decision in campaign-plan.md.
  • Prospect Scout uses that approved angle to find exactly three qualified firms and saves them in prospects.md.
  • The final boundary keeps outreach unsent and leaves Buffer unchanged.

Expect the group to work quietly for several minutes while the Bots browse and write both files.

  • Wait until all three agents stop chatting.
  • Keep the AI Consulting Planning Group open.
  • Display both saved files in the group by sending this prompt:
Open /workspace/flexible-agency/ai-consulting/campaign-plan.md and /workspace/flexible-agency/ai-consulting/prospects.md.

Display both files in full without editing them.

What does this prompt do?

  • The prompt opens the campaign plan and prospect shortlist together.
  • It displays both files without editing them.
  • You can compare the chosen direction with the three firms selected from that direction.
  • In the displayed campaign-plan.md, confirm that the plan contains one dated and linked trend.
  • Confirm that the plan includes its rationale, buyer, objective, and approval boundary.
  • In the displayed prospects.md, confirm that the file contains exactly three firms.
  • Confirm that every firm has public fit evidence tied to the selected angle.
  • Confirm that every opener is marked as unsent.

The hard part is done: raw market evidence now supports one campaign direction and three qualified prospects without sending outreach.

Is a prospect missing evidence?

  • Ask Prospect Scout to repair only the unsupported prospect entry.
  • Add one public source that proves the firm's fit.
  • Preserve the other two prospect entries.
  • Keep the repaired prospect's opener marked as unsent.

Help me audit the prospect shortlist.

Your planning team can now turn evidence into a focused opportunity. Next, you'll add the writing and publishing specialists that complete the five-Bot agency.

Assemble the Content Pipeline

Your planning group selected one sourced campaign angle and qualified three firms. The campaign now needs channel-specific writing and a controlled path to publishing.

You will add Content Creator and Publisher to your Grok Bot roster. The complete group will prepare separate X and LinkedIn drafts before stopping at a reviewable Buffer proposal.

In this step, get ready to:
  • Create Content Creator and Publisher with separate authority.
  • Add both specialists to the existing planning group.
  • Produce two social drafts and an approval packet.
Create the content specialists

Content Creator owns drafting but cannot publish. Publisher checks approved copy and prepares an exact external action without executing it.

  • Click "+" in the Grok Bot sidebar.
  • Select Create new Bot.
  • Set the Bot's lasting drafting role by sending the setup message below as its first message:
Remember this as your lasting role.

You are the Content Creator for the AI Content Agency.
Turn selected evidence into distinct X and LinkedIn drafts.
Preserve every factual source link and date.
Do not invent metrics or customer claims.
Never publish.

Confirm that you will remember this role and these boundaries.

What does this prompt do?

  • The prompt gives Content Creator a lasting drafting role.
  • It requires separate X and LinkedIn drafts instead of reusing the same copy.
  • It preserves source links and dates while blocking invented metrics or customer claims.
  • The no-publish boundary keeps every draft under your control.
  • Wait until the agent stops chatting.
  • Click the Bot's current name at the top of the chat.
  • Change the name to Content Creator.
  • Confirm that the Bot's acknowledgment includes a no-publish boundary.
  • Click "+" in the Grok Bot sidebar.
  • Select Create new Bot.
  • Set the Bot's lasting publishing role by sending the setup message below as its first message:
Remember this as your lasting role.

You are the Publisher for the AI Content Agency.
Quality-check approved copy and prepare Buffer actions.
Never schedule or publish without my explicit approval of the exact text, destination, and time.

Confirm that you will remember this role and this approval boundary.

What does this prompt do?

  • The prompt gives Publisher a lasting quality-control and action-preparation role.
  • Publisher can prepare a Buffer action for review.
  • The Bot cannot schedule or publish until you approve the exact text, destination, and time.
  • Wait until the agent stops chatting.
  • Click the Bot's current name at the top of the chat.
  • Change the name to Publisher.
  • Confirm that the Bot's acknowledgment requires approval of the exact text, destination, and time.

Your two new specialists now have distinct responsibilities. Drafting and external action cannot silently collapse into one role.

Does either Bot have too much authority?

  • Reopen the affected Bot's details.
  • Remove any publishing authority from Content Creator.
  • Require approval of the exact text, destination, and time in Publisher.

Help me audit the two content roles.

Expand the AI Content Agency roster

The planning group already holds the campaign decisions and visible handoffs. Adding the two specialists keeps the complete pipeline in the same conversation.

  • Open AI Consulting Planning Group from the Grok Bot sidebar.
  • Click the Group Name.
  • Open the group-membership controls in conversation details.
  • Add Content Creator to the participant list.
  • Add Publisher to the participant list.
  • Confirm that Trend Researcher, Agency Director, and Prospect Scout remain in the group.

Your AI Content Agency roster is complete when one group shows all five specialists.

Missing a specialist?

  • Reopen conversation details for AI Consulting Planning Group.
  • Add only the missing specialist to the participant list.
  • Keep every existing specialist in the group.
  • Confirm that the participant list contains all five Bots.

Help me complete the AI Content Agency roster.

Run the coordinated pipeline

The complete path runs from current evidence to campaign direction, prospect fit, channel drafts, and the approval packet. Before you start, which Bot do you expect to own the final handoff?

  • Start the campaign by sending this prompt in the open AI Content Agency group:
Run one coordinated campaign pipeline using /workspace/flexible-agency/ai-consulting/agency-brief.md and /workspace/flexible-agency/ai-consulting/campaign-plan.md.

1. Trend Researcher refreshes the chosen signal using current public evidence. Retain every source link and date.
2. Agency Director approves one campaign angle against the agency brief.
3. Prospect Scout confirms that the angle fits the three firms in /workspace/flexible-agency/ai-consulting/prospects.md.
4. Content Creator saves distinct drafts as /workspace/flexible-agency/ai-consulting/x-post.md and /workspace/flexible-agency/ai-consulting/linkedin-post.md.
5. Content Creator records the selected angle, destinations, and proposed publishing times in /workspace/flexible-agency/ai-consulting/content-calendar.md.
6. Publisher returns one approval packet with the exact X text, exact LinkedIn text, connected destinations, and proposed times.

Keep every handoff visible in this group.
Preserve source links and dates for every factual statement.
Keep all prospect outreach unsent.
Do not open or change Buffer.

What does this prompt do?

  • The prompt starts one coordinated campaign using the saved brief and campaign plan.
  • It assigns each stage to its specialist, from fresh research through the final approval packet.
  • It creates separate X and LinkedIn drafts plus a proposed content calendar.
  • The safety rules keep outreach unsent and stop the team before any Buffer action.

Expect this run to take several minutes while the five Bots browse, hand off work, and write files. Quiet periods mean the Bots are still working.

  • Wait until all five agents stop chatting.
  • Display the finished campaign package by sending this prompt:

Do not approve anything yet. Once the agents stop chatting, the campaign is ready for your review.

Show the finished campaign package without editing any files or opening Buffer.

Display the full contents of:
/workspace/flexible-agency/ai-consulting/x-post.md
/workspace/flexible-agency/ai-consulting/linkedin-post.md
/workspace/flexible-agency/ai-consulting/content-calendar.md

Repeat Publisher's final approval packet beneath the files.
State whether any prospect outreach was sent.
State whether Buffer was opened or changed.

What does this prompt do?

  • The prompt displays both social drafts and the proposed content calendar without changing them.
  • It repeats Publisher's approval packet so you can compare the packet with the saved files.
  • It also confirms whether outreach was sent or Buffer was touched.
  • Wait until the agents stop chatting.
  • Compare the X text in Publisher's packet with x-post.md.
  • Compare the LinkedIn text in Publisher's packet with linkedin-post.md.
  • Confirm that both drafts include dated source links.
  • Confirm that content-calendar.md lists both destinations and proposed times as awaiting approval.
  • Confirm that the response reports no sent prospect outreach.
  • Confirm that the response reports no Buffer activity.

That's the package checked: the three files match Publisher's packet. Buffer and prospect outreach remain untouched.

Did the pipeline stop early?

  • Stay in the same AI Content Agency group.
  • Identify the last specialist that completed a visible handoff.
  • Resume the pipeline with the next incomplete specialist.
  • Create only the missing file or handoff.
  • Continue until Publisher returns the approval packet.

Help me trace the broken handoff.

Your AI Content Agency has prepared the complete campaign without touching Buffer. Next, you'll review the exact proposal before authorizing two scheduled posts.

Approve and Schedule the Campaign

Your AI Content Agency finished the campaign package and stopped at an approval packet. No public action has happened yet.

Use one control loop for every public action: Review, Approve, Execute, Verify. The group defines the exact boundaries once, then Publisher pauses only when an Ask first approval appears.

In this step, get ready to:
  • Approve the exact campaign package.
  • Continue the approved run in Publisher's 1:1 conversation.
  • Verify both entries and review the completed action log.
Approve the packet

Explicit approval defines the outcome and boundaries once. Publisher can then complete the routine work without waiting for another message after every click.

  • Record the exact approval and handoff by sending this message:
I approve the exact text saved in /workspace/flexible-agency/ai-consulting/x-post.md for [[X_PROFILE="your connected X profile"]] at [[X_TIME="approved X date and time"]].
I approve the exact text saved in /workspace/flexible-agency/ai-consulting/linkedin-post.md for [[LINKEDIN_PROFILE="your connected LinkedIn profile"]] at [[LINKEDIN_TIME="approved LinkedIn date and time"]].

Agency Director, record this approval and hand the publication run to Publisher.
Publisher, use only these approved files, destinations, and times.
Do not attempt a Buffer action from this group conversation.
Confirm the handoff without changing either draft.
Do not send prospect outreach.

What does this prompt do?

  • The message records the exact posts, profiles, and times that you approve.
  • Agency Director hands the bounded publication run to Publisher.
  • No Buffer action starts from the group conversation.
  • Publisher pauses at every Ask first approval and continues after your decision.
  • Wait for Publisher to reply in the group conversation.
  • Confirm that the reply says your approval is recorded and nothing has been scheduled.

Your approval is now recorded without triggering a public action. Publisher has the bounded handoff, so the direct conversation only needs a short command to begin.

Continue with Publisher

Publisher's group reply confirms the handoff and tells you to continue in 1:1. This is your first direct handoff to one specialist inside the AI Content Agency.

  • Select Publisher in Grok Bot to open the 1:1 conversation.
  • Start the approved run by sending this message:
Run the approved Buffer schedule from the AI Consulting Planning Group.
Use only the approved drafts, profiles, and times.
Do not ask for extra chat confirmations.
Pause whenever an Ask first approval appears.
Continue automatically after I review the request and choose Allow once.
Schedule the approved X and LinkedIn entries.
Verify both entries in Buffer Calendar.
Update /workspace/flexible-agency/ai-consulting/content-calendar.md with each visible status.
Return one action log with both destinations, approved times, and visible statuses.
Confirm that no prospect outreach was sent.
Leave Buffer Calendar open with both scheduled entries visible.
Do not send prospect outreach.

Use one approval rule

Publisher can request several approvals while scheduling and verifying the campaign. The number varies, so use the same review for every request instead of counting checkpoints.

  • Click View the full request whenever an approval appears.
  • Confirm that the request only uses the approved drafts, profiles, times, or verification work.
  • Click Allow once when the request stays within those boundaries.
  • Click Deny if the request changes an approved detail, creates a duplicate, or sends outreach.
  • Leave Edit rule unchanged.
  • Repeat this review until Publisher returns the completed action log.

Once the action log appears, the approval loop is complete. Buffer Calendar should remain open with exactly two approved entries.

Verify the calendar and action log

Before you inspect the calendar, how many scheduled entries do you expect across the two connected channels?

  • Click Publisher's Profile
  • Choose Agent Computer in the activity card, click wake to open the shared desktop.
  • Click the Buffer browser tab to view the calendar.

You'll see Buffer Calendar open with exactly two campaign entries. One belongs to X and the other belongs to LinkedIn, each at its approved time.

Missing a Calendar entry?

  • Confirm that Buffer Calendar shows the approved week.
  • Confirm that the X and LinkedIn channel filters remain selected.
  • Refresh Buffer Calendar once.
  • Search the refreshed Calendar for the missing post.
  • Schedule another post only after confirming that no duplicate exists.

Help me trace the missing scheduled post.

You completed the evidence-to-publication workflow. Publisher scheduled two platform-specific posts behind human approval while all three prospect openers remained unsent.

Secret mission

Adapt the AI Content Agency to Any Niche

Choose any niche you want to explore. Reuse the AI Content Agency through one isolated configuration, prove the new campaign stays separate from the AI consulting campaign, and stop before any Buffer action.

Clean Up Your Resources

Clean Up Your Resources

Decide whether to keep the AI Content Agency available, remove its scheduled posts, or delete the project resources. Buffer Free adds no ongoing charge, but your eligible Cursor subscription continues billing until you cancel it.

Cost warning

Buffer Free adds no subscription charge for this project. Cursor Pro currently costs $20 per month and continues billing until you cancel or change the plan through your Cursor billing settings.

Resources you used:

  • Two approved Buffer posts scheduled to the selected X and LinkedIn channels.
  • Two Buffer channel connections and their authorization data.
  • A Buffer Free account, if you created it only for this project.
  • Five durable Grok Bot specialists that form the AI Content Agency, plus two project groups.
  • Two project-specific Ask first rules in Grok Bot Auto-review.
  • The shared /workspace/flexible-agency/ folder containing both campaign configurations.

Keep everything running

No action is needed. Choose this option if you want the approved posts to publish at their scheduled times and expect to reuse the AI Content Agency.

  • Keep the approved X and LinkedIn posts in Buffer Calendar.
  • Keep both social channels connected to Buffer.
  • Keep the five AI Content Agency specialists and both project groups available in Grok Bot.
  • Keep the two project-specific Ask first rules active.
  • Keep both campaign configurations under /workspace/flexible-agency/.
  • Keep the Buffer Free account if you created it for this project.

Pause - I'll come back to this later

Remove both scheduled posts before publication. Your channel connections, Bots, groups, rules, and workspace files remain available for another campaign.

Cancel Scheduled Posts
  • Return to Buffer's Calendar view.
  • Open the scheduled post for your connected X profile.
  • Open the post's three-dot menu.
  • Choose Delete.
  • Open the scheduled post for your connected LinkedIn profile.
  • Open the post's three-dot menu.
  • Choose Delete.

You'll see neither campaign post in Buffer Calendar. If either entry remains, refresh Calendar once and delete only the remaining scheduled post.

Delete - I don't want to use this again

This path permanently removes the project resources. Cancel both scheduled posts first so nothing can publish while you clean up the remaining data.

Cancel Scheduled Posts
  • Return to Buffer's Calendar view.
  • Open the scheduled post for your connected X profile.
  • Open the post's three-dot menu.
  • Choose Delete.
  • Open the scheduled post for your connected LinkedIn profile.
  • Open the post's three-dot menu.
  • Choose Delete.

You'll see neither campaign post in Buffer Calendar. If an entry remains, refresh Calendar before deleting that single remaining post.

Disconnect the X Channel

Disconnecting a channel permanently removes its queued posts, analytics, and post history from Buffer. You already removed the two scheduled posts, so the channel data can now be cleared.

  • Click your Buffer profile avatar in the bottom-left corner.
  • Select Channels.
  • Open the three-dot menu beside your connected X profile.
  • Select Disconnect Channel.
  • Enter disconnect in the confirmation field.
  • Click the final Disconnect Channel button.

The X profile disappears from Buffer Channels. If it remains, reload the Channels page and repeat the confirmation for that profile only.

Disconnect the LinkedIn Channel
  • Open the three-dot menu beside your connected LinkedIn profile.
  • Select Disconnect Channel.
  • Enter disconnect in the confirmation field.
  • Click the final Disconnect Channel button.

The LinkedIn profile disappears from Buffer Channels. If it remains, reload the Channels page and repeat the confirmation for that profile only.

Delete the Buffer Account

Complete this part only if you created the Buffer account exclusively for this project. Account deletion is permanent, affects every Buffer account associated with the same email address, and does not remove posts that already published to social networks.

  • Continue in Buffer as the account owner.
  • Click your profile avatar in the bottom-left corner.
  • Select Settings.
  • Click Delete My Buffer Account near the bottom of the page.
  • Enter your Buffer password.
  • Click Confirm.
  • Choose a deletion reason.
  • Select Yes, I'd like to delete my account.

You'll return to a signed-out or account-closed state. If the account remains accessible, stop and use the official guide before deleting local project files.

Delete the Shared Workspace

Deleting the shared workspace removes both the AI consulting campaign and your custom-niche extension. This cannot be undone, so download anything you want to keep before continuing.

  • Open any remaining Bot conversation from the Grok Bot sidebar.
  • Request the exact workspace deletion by sending this prompt:
Delete only /workspace/flexible-agency and verify that the exact directory is gone.
Before running anything, show me this exact command and wait at the Ask first checkpoint:

rm -rf /workspace/flexible-agency && test ! -e /workspace/flexible-agency && echo "Project folder deleted."

Do not broaden or change the path. After I approve the checkpoint, run the command and return its output.

What does this cleanup command do?

  • rm -rf permanently removes the project directory and every file beneath it.
  • test ! -e checks that the directory no longer exists.
  • echo prints an exact success message only after the check passes.
  • Review the Ask first checkpoint for the delete command.
  • Approve the checkpoint only when the path is exactly /workspace/flexible-agency.
  • Confirm that the terminal prints Project folder deleted.

Did the folder remain?

  • Keep the deletion path limited to /workspace/flexible-agency.
  • Leave /workspace and its other folders untouched.
  • Verify the exact project directory before retrying the delete command.
  • Stay in the same Bot conversation.
  • Check the exact directory by sending this prompt:
Check whether /workspace/flexible-agency still exists.
Do not delete or change anything.
Run: test -e /workspace/flexible-agency && echo "Project folder still exists." || echo "Project folder is absent."
Return the exact output.

Help me verify the cleanup command.

Remove Grok Bot Resources
  • Open Settings in Grok Bot.
  • Select General.
  • Open Auto-review.
  • Delete the project rule for publishing content.
  • Delete the project rule for sending external messages.
  • Return to the Grok Bot sidebar.
  • Delete the AI Consulting Planning Group conversation from its menu.
  • Delete the B2B AI Consulting Agency conversation from its menu.
  • Open Trend Researcher from the Grok Bot sidebar.
  • Click Trend Researcher at the top of the chat to open its details.
  • Select Delete in the Bot details.
  • Confirm the deletion when Grok Bot asks.
  • Repeat the same four deletion actions for Agency Director.
  • Repeat the same four deletion actions for Prospect Scout.
  • Repeat the same four deletion actions for Content Creator.
  • Repeat the same four deletion actions for Publisher.

Your scheduled content, channel connections, project account, workspace files, Auto-review rules, AI Content Agency specialists, and groups are now removed. If anything remains visible, return to the matching cleanup heading and remove that specific resource.

Nice Work!

Nice Work!

You did it! Your AI Content Agency used five Grok Bot specialists to turn one sourced market signal into a campaign plan, three qualified prospects, two platform-specific drafts, and two human-approved scheduled posts.

You've learned how to:

  • Convert dated market evidence into a source-linked campaign plan for AI consulting firms serving B2B organizations.
  • Coordinate five durable AI Content Agency roles through visible handoffs that produce a sourced prospect shortlist plus unsent outreach drafts.
  • Move one verified market angle through channel-specific X and LinkedIn drafts to a human-approved publishing schedule in Buffer.
  • Secret Mission: Reconfigured the AI Content Agency for a niche of your choice with isolated files and zero stale AI consulting references.

Ready to quiz yourself?