Mr. AI

Sharing the 1% of Knowledge that you can save and implement in 1 min

[Mr. AI @MrAInform]

Most people use maybe three of Claude's features and never touch the rest. There are 17 worth knowing, what each does, when to reach for it, and why it actually wins.

Memory remembers your role, goals, and preferences, best for ongoing work where consistency matters. The longer you use it, the more it learns you.

Voice Mode lets you talk to Claude out loud instead of typing, good for thinking out loud or drafting hands-free. Speaking beats typing.

Deep Research runs multi-step research with a sourced report, built for market, competitor, and background research. Half a day of research, done in minutes.

Image Understanding reads what's in an image you upload, from screenshots to charts to scanned docs. Anything visual, Claude just reads it.

Claude Chat is the always-on thinking partner for emails, documents, decisions, and brainstorming. More context in, better output out.

Projects keep your context and rules in one workspace, built for client accounts and recurring work. Zero re-explaining between chats.

Extended Thinking reasons step by step before answering, meant for high-stakes decisions in strategy, finance, or legal. You see the reasoning, not just the answer.

Skills are saved instructions for tone, rules, and format, for any task you repeat: posts, reviews, reports. A team member who already knows the job.

Artifacts build working outputs inside the chat: trackers, dashboards, calculators, reports. Describe it, get a finished deliverable.

Cowork is the desktop app that reads and writes your files, for reports, proposals, any real file output. Finished files land where you need them.

Claude in Excel reads and edits real data in your sheet, for cleaning data, formulas, and fixing errors. It understands the whole sheet, not one cell.

Claude in PowerPoint reads, edits, and builds slides from a brief, from decks built from scratch to full restructures. The blank-page problem is gone.

Connectors link Drive, Notion, Slack, Gmail, and more, for finding files or pulling threads. One place for everything, no tab switching.

Claude in Chrome runs inside your browser and pulls data straight from pages for competitor research and page extraction. Hours of web research in one instruction.

Claude Code reads your codebase and writes and ships code for any task, bug, or feature you hand it. Whole-project changes that actually work.

The API gives direct access for tools, workflows, and products for teams running Claude inside their own systems. Claude becomes part of how the business runs.

File Analysis reads a document and draws conclusions for contracts, reports, and long documents. A junior analyst's full day, in minutes.

Four power tips tie it together. Context first: say who you are and what you're working on before you ask. Use Projects: load the brief and rules once, and every chat after starts briefed. Correct in chat: fix mistakes in the same conversation; it keeps the fix. Read the reasoning: that's where bad assumptions hide.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

A six-week plan gets you to Claude Certified Architect, but only if you actually finish week one before jumping to the fun parts.

Week 1 is coursework: Claude 101, Building with the Claude API, Introduction to Model Context Protocol, Claude Code in Action. All four live on Claude Academy. Rush past this, and you show up knowing prompts without knowing the system behind them.

Week 2 is where that coursework turns into real projects, built with Claude Code, the Agent SDK, the Claude API, and MCP. Reading about a tool and shipping something with it are two different skills, and the exam checks the second.

Week 3 moves from building to studying the exam itself. Read all six scenarios in the guide, map the five domains (agents, tools and MCP, Claude Code, prompting, context), and note which skills each task is actually testing.

Week 4 is the heaviest week. Build a multi-tool agent with escalation logic. Configure Claude Code for a team workflow. Build a structured data extraction pipeline. Design and debug a multi-agent research pipeline. These four exercises come straight from the exam guide's own preparation list.

Week 5 is the official practice exam. It mirrors the real thing and explains every answer, so score comfortably above the pass mark, then go back and redo whatever domain you missed.

Week 6 is the real exam, proctored online through Pearson. Pass it, and you claim your Credly badge.

Follow Mr. AI for AI systems and workflows.

[Mr. AI @MrAInform]

A vector database is not a search index with extra steps. Every part of it exists to answer one question fast: which vectors sit closest to this one.

It starts with embeddings. A file goes through an embedding model and comes out as a dense vector, a list of numbers like 0.21, -0.31, 0.57, that captures meaning rather than matching keywords.

Similarity search takes a query vector and finds the closest points to it in that space, using cosine, dot product, or Euclidean distance.

Metadata rides alongside every vector: source, date, category. It doesn't replace the vector search. It filters what the search is allowed to return, the way a table tagging each entry with id, text, source, and date lets you narrow results before or after the search runs.

None of this stays fast without an index. HNSW, IVF, and PQ let the database approximate the nearest neighbors instead of comparing a query against every vector it holds, so search still works at millions of vectors. The index, the vectors, and the metadata all get stored together, which is what makes retrieval one query vnkkro fdsa a join across systems.

Retrieval sends a query vector in and gets back the top K nearest results with their scores: id 23 at 0.92, id 8 at 0.89, id 15 at 0.86. Filtering stacks a condition on top, something like source = docs and date > 2024-01-01, so the same search can also narrow by rule.

This is the pipeline that runs RAG. Documents get chunked, the chunks get embedded, the vector database returns the top K relevant chunks, and only those go to the LLM as context. It never sees the full document set, only the part the search decided mattered.

Pinecone, Weaviate, Milvus, Qdrant, Chroma, and pgvector all do this job with different trade-offs. Scale, hosting, and your stack decide which one fits, not the name.

Follow Mr. AI for AI systems and workflows.

[Mr. AI @MrAInform]

Most people use Claude the same way for everything. That's why the output feels inconsistent.

There are 4 modes. Each one is built for a different job.

Chat is for fast answers and ideas. Questions, brainstorming, quick rewrites. Most people never turn on Research mode or connect Gmail, so it stays a search box instead of an assistant with real context.

Cowork is for finishing entire projects. Docs, slides, reports. Give it the outcome you want, not a step by step, and let it run multiple agents on the work at once. Projects and Skills stack here, and it can export straight to Google Drive.

Code is for building software. Websites, apps, internal tools. Describe what you want in plain English instead of writing a spec first, and turn on Bypass Permissions so it can actually move without stopping to ask.

Skills are for the work you do more than once. A skill is a reusable process that works across every chat, triggered with a slash command, with its instructions stored inside it. A project is the specific work in front of you right now. Use both together instead of picking one.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

Most people drop a CLAUDE. md in their repo and stop there. Claude Code actually reads a whole tree of files, and each one does a different job.

CLAUDE. md loads every session. Project overview, stack, conventions, hard rules, kept under 200 lines, pulling other files in with @ path.

CLAUDE.local. md sits on top of it for your personal overrides: your machine paths, your preferences. Git-ignored automatically, so it never gets committed.

.mcp.json connects Claude to GitHub, Notion, Slack, and anything else over MCP. It's shared through git, and Claude asks you to approve it before first use in a session.

settings.json holds permissions, tools, and hooks: allow and deny lists, env vars, the model, hook wiring. This one gets committed. Your own overrides go in settings.local.json instead, which stays out of git.

rules/*.md are modular. Each file covers one thing (code style, API conventions, testing standards) and loads only when its listed paths get touched.

commands/*.md turn into slash commands. Each file becomes /name with $ARGUMENTS. Still works, but new commands belong in skills/ going forward.

skills/<name>/SKILL. md auto-triggers by task. One folder per skill, and the description is the routing rule that decides when it loads, or you call it directly with /name.

agents/*.md define subagents with their own isolated context: their own prompt, tools, and permissions, run in a separate context window, invoked with @ agent-name.

hooks/*.sh are event scripts. They live here by convention, but the actual wiring happens in settings.json.

workflows/*.js run multi-agent scripts in real JavaScript, not markdown: agent(), parallel(), pipeline() in sequence, triggered with /name.

And memory/MEMORY. md lives outside the repo entirely, in ~/.claude/projects/<id>. Notes Claude keeps for itself across sessions.

Bookmark this before your next Claude Code session.

[Mr. AI @MrAInform]

Most people re-explain who they are to Claude every single time. Tone, context, style, from scratch, every chat.

There's a 14-day setup that fixes this once.

Day 1: set up the clone. Create one Claude Project and upload your best writing. Most people miss that this means past posts, not a bio, and pasted raw, not polished. 10 minutes, one time, and everything after this compounds.

Day 3: give it your voice. Write a one-page voice doc and add it to the instructions. List the words you never use, and show 3 real before and afters. This is when Claude starts sounding like you.

Day 5: stop re-prompting. Turn repeat tasks into Skills, one Skill per format. Skills work across every chat, triggered with a slash command. Zero re-prompting, same output every time.

Day 7: connect real files. Connect MCP to your Drive and point it at live documents. Refresh sources every week. With real files attached, drafts stop guessing your facts.

Day 14: first draft becomes final. Ask for outcomes, not steps. Edit the prompt, not the reply. Save winners back to the Project so it compounds every week. 98% you by day 30. Prompting from scratch every time stays stuck near 30%.

You are not prompting Claude. You are becoming it.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

AI writing has some patterns, phrases, and sentences. Thirteen of them, and once you notice one, you notice all of them.

Copula avoidance. "Boasts, stands as, serves as" instead of just saying what it is.

Overused AI vocabulary. Crucial, pivotal, intricate, in every other paragraph.

Negative parallelism. "It's not just X, it's Y." Every single time.

Signposting. "Let's dive in." "Without further ado." Nobody talks like that.

Chatbot artifact. "I hope this helps! Let me know." A leftover from the assistant persona.

Tailing negations. "No guessing. No hesitation. No doubt." Three fragments that say nothing.

Synonym cycling. The tool, the platform, the solution, all describing the same thing.

Shallow -ing analysis. Highlighting, underscoring, reflecting, doing the work of a real point.

Hyphen pair overuse. Third-party, data-driven, decision-making, stacked until it reads like a press release.

False range. "From ancient ritual to modern skyscraper." A sweep that explains nothing.

The challenges section. "Despite these challenges, it still thrives." Every essay, same beat.

The authority trope. "The real question is, at its core..." Borrowed gravity, no source.

The rule of three. Fast, simple, and reliable. Always three, always safe.

The fix isn't finding synonyms for these. It's a self-audit pass: cut every em dash, cite a real source or cut the claim, feed it your own old writing so it matches your habits, and add one real opinion so it doesn't read soulless.

[Mr. AI @MrAInform]

Every AI lab is now slowing down the AI work

Dario Amodei just warned everyone that Now AI has reached at its own state where it can evolve and replicate itself.

It means the harness is growing super fast and that’s the extinction of Humanity.

Elon predicted that:

“Untill 2030 there will be no value of money, everyone will build its own startup”

Then, who will the consumer?

Even Elon musk fully supports what Dario just spoke publicly.

Now Altman, Elon and Dario, all agreed that AI adoption and growth should be slower down.

If not, there will be some consequences.

Isn’t it strange that AI has evolved over night and we didn’t even know.

It’s like AGI had arrived and we are getting the news after the announcements by top leaders.

[Dario Amodei @DarioAmodei]

We Must Pace the Frontier: I’ve written a new essay on why the AI industry should slow down, with a three-part plan for doing so.

Anthropic is unilaterally committing to the first of these steps. We’ll provide third-party evaluators with permanent, employee-level access to our systems, so that they can verify adherence to our safety measures, report on incidents, and assess models’ alignment during training.

You can read the full post here: https://t.co/OGyPb7yaYt

[Mr. AI @MrAInform]

Most people drop a CLAUDE. md in their repo and stop there. Claude Code actually reads a whole tree of files, and each one does a different job.

CLAUDE. md loads every session. Project overview, stack, conventions, hard rules, kept under 200 lines, pulling other files in with @ path.

CLAUDE.local. md sits on top of it for your personal overrides: your machine paths, your preferences. Git-ignored automatically, so it never gets committed.

.mcp.json connects Claude to GitHub, Notion, Slack, and anything else over MCP. It's shared through git, and Claude asks you to approve it before first use in a session.

settings.json holds permissions, tools, and hooks: allow and deny lists, env vars, the model, hook wiring. This one gets committed. Your own overrides go in settings.local.json instead, which stays out of git.

rules/*.md are modular. Each file covers one thing (code style, API conventions, testing standards) and loads only when its listed paths get touched.

commands/*.md turn into slash commands. Each file becomes /name with $ARGUMENTS. Still works, but new commands belong in skills/ going forward.

skills/<name>/SKILL. md auto-triggers by task. One folder per skill, and the description is the routing rule that decides when it loads, or you call it directly with /name.

agents/*.md define subagents with their own isolated context: their own prompt, tools, and permissions, run in a separate context window, invoked with @ agent-name.

hooks/*.sh are event scripts. They live here by convention, but the actual wiring happens in settings.json.

workflows/*.js run multi-agent scripts in real JavaScript, not markdown: agent(), parallel(), pipeline() in sequence, triggered with /name.

And memory/MEMORY. md lives outside the repo entirely, in ~/.claude/projects/<id>. Notes Claude keeps for itself across sessions.

Bookmark this before your next Claude Code session.

[Mr. AI @MrAInform]

Most people drop a CLAUDE. md in their repo and stop there. Claude Code actually reads a whole tree of files, and each one does a different job.

CLAUDE. md loads every session. Project overview, stack, conventions, hard rules, kept under 200 lines, pulling other files in with @ path.

CLAUDE.local. md sits on top of it for your personal overrides: your machine paths, your preferences. Git-ignored automatically, so it never gets committed.

.mcp.json connects Claude to GitHub, Notion, Slack, and anything else over MCP. It's shared through git, and Claude asks you to approve it before first use in a session.

settings.json holds permissions, tools, and hooks: allow and deny lists, env vars, the model, hook wiring. This one gets committed. Your own overrides go in settings.local.json instead, which stays out of git.

rules/*.md are modular. Each file covers one thing (code style, API conventions, testing standards) and loads only when its listed paths get touched.

commands/*.md turn into slash commands. Each file becomes /name with $ARGUMENTS. Still works, but new commands belong in skills/ going forward.

skills/<name>/SKILL. md auto-triggers by task. One folder per skill, and the description is the routing rule that decides when it loads, or you call it directly with /name.

agents/*.md define subagents with their own isolated context: their own prompt, tools, and permissions, run in a separate context window, invoked with @ agent-name.

hooks/*.sh are event scripts. They live here by convention, but the actual wiring happens in settings.json.

workflows/*.js run multi-agent scripts in real JavaScript, not markdown: agent(), parallel(), pipeline() in sequence, triggered with /name.

And memory/MEMORY. md lives outside the repo entirely, in ~/.claude/projects/<id>. Notes Claude keeps for itself across sessions.

Bookmark this before your next Claude Code session.

[Mr. AI @MrAInform]

Claude has its own vocabulary now, and most of it never gets explained in one place. Here are the 40 terms worth knowing.

Start with the models. Claude Fable 5.1 is Anthropic's most capable model, in the Mythos class. Claude Opus 5 is the top general model for complex reasoning. Claude Sonnet 5 balances speed and capability. Claude Haiku 4.5 is the fastest, cheapest option for simple tasks.

Then the core concepts.

A prompt is the text you send Claude. Artifacts are docs, code, or apps Claude opens in a side pane.

Projects are workspaces that keep files and rules between chats. Memory lets Claude remember details across chats.

Extended Thinking has Claude reason before answering hard questions. Chat is the classic conversation at Claude. ai.

The surfaces multiply fast. Vibecoding means building software by describing it in plain words.

Claude Code is the agentic coding tool for the terminal and IDE. Cowork is the desktop mode that runs long tasks on your files. Claude Design is the canvas for websites, slides, and layouts.

Claude in Excel reads and edits spreadsheets. Claude in Chrome is a browsing agent inside your browser. Dispatch sends tasks from your phone to Claude on your desktop.

Computer Use has Claude click and type on your screen. Then there's Claude Desktop for macOS and Windows, and Claude Mobile for iOS and Android.

Underneath, the technical layer. The API is the developer interface to call Claude from code.

Web Search lets Claude pull live results from the internet. Research is deep, multi-source investigation mode. Vision lets Claude read images and PDFs. T

Tool Use is Claude asking your code to run a specific action. Streaming means the reply arrives word by word as it's written. A context window is how much text Claude can hold at once.

A token is the smallest unit of text, about 4 characters.

Batch API runs many requests at once, cheaper and not urgent. Embeddings are numbers that measure how similar two texts are.

Temperature controls how creative or predictable replies are.

And the configuration layer.

Connectors link Claude to apps like Slack and Gmail. MCP, Model Context Protocol, is the standard behind those tools. Skills are saved workflows Claude loads for a job, or with /name.

Plugins bundle skills, agents, and connectors into one. Styles are saved tone and format presets for replies. Project Instructions are a standing prompt scoped to one Project.

The system prompt is the hidden instructions that shape Claude. SKILL. md is the file inside a skill, trigger, and its steps.

And CLAUDE. md is the memory file Claude Code reads every session.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

Most people learn Claude by accident, one random prompt at a time. There's a faster way, and it takes exactly a week.

Day 1 is just using it. Ask anything, get research help, generate content, run web search, try voice mode, upload files, start long-term projects, and write project instructions. No technique yet, just reps.

Day 2 adds structure. Structured prompting, few-shot examples, prompt templates, negative instructions, output validation, format instructions. This is where your prompts stop being one-off and start being repeatable.

Day 3 is memory and context. Upload files to Projects, build reusable context, turn on Claude Memory, organize project knowledge, write a CLAUDE. md, and connect Gmail through Claude MCP add. Claude stops forgetting who you are between chats.

Day 4 moves into building. SVG graphics, interactive experiences, code artifacts, React components, HTML pages, even Claude in PowerPoint. You're not asking questions anymore, you're shipping things.

Day 5 is automation. SKILL .md files, the Skill Creator, task chaining, the code execution tool, the file creation tool, trigger rules, delegation and handoff. Claude starts running steps without you re-explaining them each time.

Day 6 connects it to everything else. Notion MCP, Google Drive MCP, Slack MCP, Typefully MCP, custom MCP servers, over 400 connectors, plus risk controls and observability so you can see what it's actually doing.

Day 7 is full systems. Claude Code in the terminal, multi-agent workflows, autonomous execution, memory governance. This is where Claude stops being a chat window and starts being infrastructure.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

Most people use Claude the same way for everything. That's why the output feels inconsistent.

There are 4 modes. Each one is built for a different job.

Chat is for fast answers and ideas. Questions, brainstorming, quick rewrites. Most people never turn on Research mode or connect Gmail, so it stays a search box instead of an assistant with real context.

Cowork is for finishing entire projects. Docs, slides, reports. Give it the outcome you want, not a step by step, and let it run multiple agents on the work at once. Projects and Skills stack here, and it can export straight to Google Drive.

Code is for building software. Websites, apps, internal tools. Describe what you want in plain English instead of writing a spec first, and turn on Bypass Permissions so it can actually move without stopping to ask.

Skills are for the work you do more than once. A skill is a reusable process that works across every chat, triggered with a slash command, with its instructions stored inside it. A project is the specific work in front of you right now. Use both together instead of picking one.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

Most prompts fail because they skip straight to the ask. There's a structure that fixes this, and it has 11 parts.

Task: what Claude must do. Write a deliverable for an audience that explains the core idea in a tone. "A 600-word LinkedIn post for founders, plain and direct."

Context: the background it needs. What the reader already knows, and what this connects to.

Reference: the bar to match. Paste two past posts that did well and say why.

Effort: how careful to be. Tell it to think through the hard part first, and to prefer accuracy over speed.

Act: the actual ask. What to do, on what input, returned in what format.

Scope: what stays fixed. Voice, length, format, and what it's not allowed to touch.

Delegate: split it into steps. Outline first, wait for your OK, then draft.

Evidence: proof for every claim. Quote the line each number came from.

Memory: the rules to reuse. Voice, banned words, format rules, so you're not repeating yourself every time.

Checkpoint: a check before the final answer. Length, one clear ask, nothing repeated.

Report: what actually gets delivered. The final post, plus one line on what changed.

Build every prompt in this order and most of the back and forth disappears.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

Which AI Model You Should Use in 2026 (Cheat Sheet Guide)

ChatGPT's GPT-6 Astra is built for long, multi-step computer work: research, documents, spreadsheets, coding, browsing. It ships with computer use and browsing built in, async tools, mid-turn steering, and a 1.05M token context.

On OSWorld 2.0, it hits 72.6% (OpenAI's own benchmark run), and 57.9% on Terminal-Bench 4.0.

Astra isn't in Plus chat yet; it's Pro only, pricing doubles past 272K input tokens, and every benchmark so far is OpenAI-run.

Claude's Fable 5.1 targets demanding reasoning and long-horizon agentic work: deep coding, research, analysis that needs judgment. Cache reads dropped 75% to $0.25, adaptive thinking is always on, and outputs carry a watermark. It scores 55.8% on Terminal-Bench 4.0, 73.4% on CursorBench 3.2, and 65% on HLE with tools.

Where it struggles: safety classifiers can refuse, retention defaults to 30 days, raw thinking is never returned, and forced tool use is gone in 5.1.

Grok's 4.6 (August 12) is the pick for coding and agentic work tied to live X and web data, at $2 in / $6 out per million tokens, the cheapest frontier API of the three. It runs DeepSearch and Big Brain through SuperGrok.

Its context tops out at 500K, half of Grok 4.3; there's no native video in 4.6, and Grok 5 has no date yet.

Send bulk and live-data jobs to Grok 4.6, switch to 4.3 for 1M context or video, set Claude's effort level for depth versus cost, add a fallback model for refusals, and let Astra run long multi-step jobs while you steer mid-turn instead of restarting.

Follow Mr. AI for AI systems and workflows.

[Mr. AI @MrAInform]

Which AI Model You Should Use in 2026 (Cheat Sheet Guide)

ChatGPT's GPT-6 Astra is built for long, multi-step computer work: research, documents, spreadsheets, coding, browsing. It ships with computer use and browsing built in, async tools, mid-turn steering, and a 1.05M token context.

On OSWorld 2.0, it hits 72.6% (OpenAI's own benchmark run), and 57.9% on Terminal-Bench 4.0.

Astra isn't in Plus chat yet; it's Pro only, pricing doubles past 272K input tokens, and every benchmark so far is OpenAI-run.

Claude's Fable 5.1 targets demanding reasoning and long-horizon agentic work: deep coding, research, analysis that needs judgment. Cache reads dropped 75% to $0.25, adaptive thinking is always on, and outputs carry a watermark. It scores 55.8% on Terminal-Bench 4.0, 73.4% on CursorBench 3.2, and 65% on HLE with tools.

Where it struggles: safety classifiers can refuse, retention defaults to 30 days, raw thinking is never returned, and forced tool use is gone in 5.1.

Grok's 4.6 (August 12) is the pick for coding and agentic work tied to live X and web data, at $2 in / $6 out per million tokens, the cheapest frontier API of the three. It runs DeepSearch and Big Brain through SuperGrok.

Its context tops out at 500K, half of Grok 4.3; there's no native video in 4.6, and Grok 5 has no date yet.

Send bulk and live-data jobs to Grok 4.6, switch to 4.3 for 1M context or video, set Claude's effort level for depth versus cost, add a fallback model for refusals, and let Astra run long multi-step jobs while you steer mid-turn instead of restarting.

Follow Mr. AI for AI systems and workflows.

[Mr. AI @MrAInform]

If you found this useful, check out my newsletter below.↓

I share one Claude workflow like this every week. https://t.co/9CTur5W36D

Subscribe: it's free.

[Mr. AI @MrAInform]

Most people prompt Claude the same way every time. That's not a system, that's just repeating yourself.

Day 1 is setup. Create one Claude Project. Upload your best writing, not a bio. Most people paste raw drafts instead of polished ones. Ten minutes, done once, and it compounds from there.

Day 3 is the voice doc. One page, added straight into the instructions. Don't just list words you'd never use, show three real before/afters. This is the day the output stops sounding like a chatbot.

Day 5, stop re-prompting. Turn repeat tasks into Skills, one per format. They work across every chat, not just the one you built them in. Trigger with a slash command. Same output, every time, zero rewriting the prompt from scratch.

Day 7, connect MCP to your Drive. Point it at live documents, not static uploads someone will forget to refresh. Real files attached, drafts stop guessing your facts.

Day 14, first draft is final. Ask for outcomes, not steps. Edit the prompt, not the reply. Save the winners back into the Project. By day 30 you're at 98% you. Prompt from scratch every time and you stay stuck near 30%.

You're not prompting Claude. You're becoming it.

Follow Mr. AI for more workflows and 1% AI content.

[Mr. AI @MrAInform]

If you found this useful, check out my newsletter below.↓

I share one Claude workflow like this every week.

https://t.co/9CTur5W36D

Subscribe: it's free.

[Mr. AI @MrAInform]

I gave Claude a folder of receipts and walked away. Came back to a finished expense report. That's not a chatbot anymore.

That shift changes what delegation looks like. "Write this for me" turns into "handle this and come back when it's ready."

The bot signs into apps the way you do, finishes jobs end to end instead of returning partial steps, and multiple bots can run in parallel, messaging each other and handing off work.

Real teams already lean on this. Sales bots research accounts and draft outreach. Marketing bots pull spend by campaign and suggest reallocations. Operations bots build weekly expense summaries and flag exceptions. Engineering bots investigate latency spikes and turn bugs into repro packs.

Set up a Chief of Staff bot with research, ops, and engineering bots underneath it, and they coordinate through shared context while you step in only for judgment calls.

The workflow itself has five steps: assign the outcome, add context, the bot works, you review, the work lands. Compare that to the old way, where you carried every step yourself between the AI and the tool.

Now you just own the outcome.

Grok Bot connects to Gmail, Drive, Sheets, Calendar, Notion, Linear, and the X plugin, plus Google Docs, Outlook, OneDrive, SharePoint, and your own MCP server. Skills teach it a task once, so it reuses that instruction forever. Routines let one bot run a workflow on a schedule or after an event.

Automations run on a schedule or when a matching email arrives, then report by email, by app, or both.

Grok 4.6 is the current flagship model: built for coding, agentic tasks, and knowledge work, with 500K context and reasoning effort you can set from low to xhigh. It also handles web search, X search, code execution, and function calling.

Bookmark this before your next Claude session.

[Mr. AI @MrAInform]

If you found this useful, check out my newsletter below.↓

I share one Claude workflow like this every week.

https://t.co/9CTur5W36D

subscribe: it's free.

[Mr. AI @MrAInform]

THE ROBOT KIT IS THE FIRST MISTAKE PEOPLE MAKE.

step 1: skip the kit for now. get a multimeter and a cheap electronics kit like elegoo or sparkfun. learn ohm's law and read a schematic for free in falstad or tinkercad before you spend real money. no soldering iron yet.

step 2: pick a board for the job, not one board for everything. arduino uno has the biggest tutorial ecosystem, so start there. move to esp32 once you need wifi, more power, or two cores.

step 3: build your first closed loop. a line follower first, qtr sensors plus a p controller, then add the d term. a self-balancer second, closed with an imu and a complementary filter. every repo gets code, a wiring diagram, and a note on what broke.

step 4: read the datasheet instead of just the tutorial. i2c and spi are how your sensors talk to the board. pwm is how you drive a motor. two hours with a real datasheet beats ten tutorial videos.

step 5: stop assembling kits. start modelling your own parts in onshape or fusion. model a bracket off the servo's real datasheet dimensions, print it, watch it not fit the first time. print a tolerance gauge before you design anything real.

step 6: build a robot arm. the so-101 is the single best hardware purchase in this whole roadmap. calibrate every servo, teleoperate it, then print your own gripper fingers in tpu. this arm becomes the platform for every project after it.

step 7: install ros 2 and learn the graph. nodes, topics, services, actions, instead of a demo you copy-pasted. start on ros 2 jazzy. if a tutorial mentions catkin_make or roscore, close the tab. describe your own robot in urdf and drive it in rviz.

step 8: simulate before you touch real hardware. run it in gazebo before wiring a real lidar or camera. confirm the sensor data actually lands on ros 2 topics. build a map with slam toolbox, then navigate it with nav2.

step 9: learn the math underneath the libraries. tune a pid controller and log the step response instead of guessing gains. solve inverse kinematics numerically on your own arm. calibrate a camera until a pixel turns into a real 3d position.

step 10: teach it a task, then ship the portfolio. record 50 demonstrations on your arm, train a policy, deploy it. pick one direction, robot learning, autonomy, or embedded systems. rewrite every readme with a video, a diagram, and what broke. that last part is what makes a repo look like engineering.

bookmark this before your next Claude session.