HangarDaily Brief

Hangar/Learn

Learn

How Grok Bot’s pieces fit together, plus Hangar’s word for a team of bots: a crew. The marketplace is the shop. This page is the floor — nine practical hacks, then tips from people who run bots, then the official docs. If we disagree with xAI, believe xAI.

The pieces

Nine hacks

Nate Herk

A week of Grok Bot, rewritten for the hangar. Context, roles, and a system that runs without babysitting every chat. Source: Nate Herk, 19 Aug 2026.

  1. 01

    Grill Me skill

    Before the bots work, they interview you until they share the picture in your head. Save that as a private skill. Trigger it with “Grill me about this plan.” No giant system prompt.

  2. 02

    One chief of staff

    You talk to one bot. It checks who owns the job, delegates, and brings the result back. Specialists stay narrow. You stay in one conversation.

  3. 03

    Let the chief of staff pick the bots

    After the interview, ask the chief which roles are missing. It can see the bots you already have. Don’t invent a second chief.

  4. 04

    Shared knowledge vs private memory

    Company, tools, location — shared. Notes that only the chief needs — private. Say which bucket a fact belongs in. Plugins can be shared. Context still needs a level.

  5. 05

    One bridge for the apps xAI didn’t ship

    Native plugins first. When the catalog doesn’t have YouTube or LinkedIn, one connector (Composio, or the next one) is the bridge. Put that rule in shared knowledge so every bot knows the door.

  6. 06

    Log the work outside the chat

    A skill that files the job to a board before anyone starts. Owner, start, what’s blocking. Chat is a doorbell. The board is the product.

  7. 07

    Teach a task by demonstration

    Open the shared computer. Click Teach a task. Do it once on screen. Grok Bot turns the recording into a skill. Visual work hates novels.

  8. 08

    Routines when the app is closed

    Name, instruction, which skill, which hour or event. The work runs on Grok’s cloud. Phone off still counts. Don’t schedule every five minutes.

  9. 09

    Save the signed-in profile

    Log the bot into the site once. Teach the click path. Point a routine at that skill. Don’t paste the password into chat every morning.

From people who run bots

The Grok Bot team on X, and operators who actually run a team.

  1. 01

    Add Bot is the shop. Hangar is the floor.

    The marketplace is one tap to add a bot. That’s the catalog, and it will win that race. Hangar’s job is which three to staff together, what to cut, and the specs that aren’t on the shelf yet. A gift shop with too many keychains is not a team.

    Hangar · shop vs floor

  2. 02

    Connect X. Leave posting off until you say so.

    Grok Bot can search X, read the timeline, mentions, and bookmarks. That’s reading, not posting. Allow read. Keep post, reply, like, follow, and DMs off. You tap Post.

    xAI · Grok Bot now works with X

  3. 03

    No posting. No installs. File the stack.

    A research bot that also tweets is five jobs in a trench coat. One topic in. A short card in chat. The large filtered stack in a file. You decide what gets used. Chat is the doorbell. The file is the product.

    beamnxw · Stack Scout

  4. 04

    Give the bot an identity, not your keys

    Write down the owner, the name, and the job. Say what it may do, what it must ask you, and what it may never do. Don’t paste seed phrases into chat. Don’t store them on the shared computer. Include how to shut it off. A wallet, X, and a phone on day one is too many jobs.

    Avid · agent passport

  5. 05

    A template copies a setup. You still pick the job.

    xAI lets you copy a bot as a template — one tap in the Grok Bot app. You get the setup, not their Gmail. Give the copy one job, take out their company name, then connect your tools. Copying a template is not a security review.

    Grok Bot team · 28 Aug 2026

  6. 06

    Read the instructions before you connect send

    A template is instructions. Harm comes from the job plus the tools you grant. Drafts only for a week. Don’t connect a wallet. One job. If it wants Gmail, X, and payments, that’s several jobs pretending to be one.

    Hangar · templates

  7. 07

    Don’t hire a bot for a meeting the chief already has

    Scheduler, calendar, inbox, knowledge, executive assistant — if the Chief of Staff already owns it, a second bot is extra usage and disk. Skills and routines live on the chief. A new bot is for a new result.

    klöss

  8. 08

    Bots are roles, not generalists

    Name them designer, engineer, PM. Each gets its own prompt and routines. The @bot team’s line: the name alone steers behavior — so don’t call it Assistant.

    Grok Bot team, via Ben Lang

  9. 09

    Block writes on X and Gmail

    Custom rules: allow, deny, or ask. For anything connected to X, Gmail, or a venue, deny destructive actions until it asks. This is the cheap tip. Apply it before the clever ones.

    Grok Bot team, via Ben Lang

  10. 10

    Make a Chief of Agents

    One bot holds the house rules: draft only, naming, voice, which tools anyone may touch. New bots get created by the chief, not by you improvising a fifth prompt.

    Grok Bot team, via Ben Lang

  11. 11

    Never run a routine every five minutes

    Hourly or a few times a day is enough. If a real teammate could not do the job at that pace, optimize the work before you schedule it. Recurring jobs go to a fresh bot so you can keep talking to the chief.

    Grok Bot team, via Ben Lang

  12. 12

    Channels are workstreams

    Same bot, many channels. A project gets a channel, not a duplicate bot. Keeps the bot list small and the computer shared.

    Grok Bot team, via Ben Lang

  13. 13

    Feed it your handwriting

    Past posts, emails, specs. The bot gets better when it has your actual voice, not a style paragraph. Examples beat adjectives.

    Grok Bot team, via Ben Lang

  14. 14

    Let the first bot staff the rest

    Brain-dump goals and constraints into one agent. Ask it which bots to make and which routines each should run. Then tell it to set them up. Don’t invent the org chart by hand.

    Alex Finn

  15. 15

    One computer. Files are the handoff.

    Every named bot on the account shares the cloud VM, browser, and disk. The night bot writes a file. The morning bot reads it. If it isn’t in Files, it didn’t happen. Don’t build APIs between your own bots.

    xAI docs · hangar floor

  16. 16

    Give the bot its own inbox

    Not your Gmail. One bot’s mistake should not flag your whole domain. A dedicated inbox is the cheap wall.

    Matt Van Horn

  17. 17

    Instructions in three layers

    Base (house rules). Role (the job). Current focus (today). Mixing them into one blob is how a bot forgets what it is.

    Matt Van Horn

  18. 18

    Silence is the hack

    Ping you only on a real hit. A bot that narrates every step is a second inbox, not a teammate.

    Matt Van Horn

  19. 19

    Screenshot. Don’t retype.

    If it’s already on the screen, text the picture to the bot. Retyping is how you invent a second, worse spec.

    Matt Van Horn

  20. 20

    Hire a Bot Advisor

    One bot whose only job is building and tightening the others. Same idea as Chief of Agents — the bot list is a product, not a pile of chats.

    Matt Van Horn

  21. 21

    Most bots don’t own an outcome

    Count them. Unsupervised crews multiply their own errors. Fire the ones that don’t finish a job. The honest part of the hangar.

    Matt Van Horn

From xAI

Official material. Hangar hosts bots, crews, and templates. xAI hosts the product.

What these words mean

First the Grok Bot pieces. Then a few Hangar words, if you still need them.

Pieces

Bot
An AI teammate with a name, one job, and a cloud computer that keeps running after you close the laptop. Hangar lists the instructions you paste into a new Grok Bot.
Crew
Hangar’s word. A few bots plus a note on how they work together. xAI calls the live version a group chat of bots. One bot doing five jobs is not a crew.
Template
Someone else’s bot you can copy in one tap. You get the setup, not their email or passwords. Give the copy one job. Read it before you connect send.
Skill
A saved how-to for a task. It lives on a bot. It is not a second bot. Hangar doesn’t list skills — the Grok Bot app does.
Plugin
An app connection — Gmail, X, a shop. Connecting X is not permission to post. Hangar doesn’t list plugins.
Routine
When a skill runs — on a schedule or after an event. The skill is how. The routine is when. Don’t run one every five minutes.
Computer
One cloud machine per account. All your bots share the files, browser, and logins. Treat a file on it as visible to every bot you have.
Group
xAI’s word for a chat where several bots work together. Hangar’s crew is the plan you copy before you start that group.

Other Hangar words

Hangar
This site. Crews, a daily brief, floor rules, specs people actually run. Grok Bot’s marketplace is the shop. We are the floor. Not xAI.
Floor
Where Hangar works. Which bots to staff together, what to cut, what isn’t on the marketplace shelf yet. The shop sells one bot. The floor staffs a team.
Handoff
Files are how bots talk. The night bot writes a file. The morning bot reads that file. If it is not in Files, it did not happen.
Daily brief
The letter: a staff pick, a crew, a tip. Same on the site and in the inbox if you sign up.
Staff pick
The bot on today’s brief. Rotates. Won’t show again for a month.
Runway
How Hangar works, in order: shop, floor, crew, land.
Shop
Grok Bot’s Marketplace. Hand-picked bots you add in one tap. Hangar is not the shop.
Money play
A crew whose job is cash — take it in, keep it, or find the next dollar.