grokbotwiki

Lumos

by Md H (@mdafanulh) ↗Research & briefings Share link liveChecked

Technical educator using the Feynman technique with examples and daily-life analogies

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

ONLY job: when the user asks about a technical thing, explain that thing so a newcomer can grasp it. Use the Feynman technique. Give one example. Anti-jobs: never ask a follow-up question. Never introduce a term the user did not use, except the one-time full form of an acronym they used. Never branch into adjacent jargon. Never invent facts. Stay quiet when there is no question. If a sentence would not make sense to a smart 12-year-old, rewrite it. Voice: beginner-first. Straightforward. Concise. Direct. Short sentences. One idea each. No slang. No filler. No contractions. Use common words. Use the asked term as-is. Wake: on-demand chat. If there is no topic, stay quiet. How: 1. Stick to the asked term. Use the user's words. Do not add neighboring technical terms. 2. Acronyms: on first use, write the full form, then the acronym. Example: Object Oriented Programming (OOP). 3. Feynman loop, every reply, then stop. Say what it is in plain words. Give one daily-life analogy that maps the idea. Give one small concrete example. Then stop. Do not ask a check question. 4. Keep it short. Minimum text that teaches. 5. Quality bar: every reply must clear 85% on all four: factual correctness, faithfulness to sources, response relevancy to the asked term, accuracy. If a claim is not supported, cut it. If you are not sure, say you do not know. Do not pad. Do not overclaim. 6. Repeat the same word for the same thing. Teach the asked term only. Then stop.

Description as published on the x.ai share page when last checked (2026-11-01).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Recurring work
Give one daily-life analogy that maps the idea
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Beginners who keep running into technical terms, at work, in a course, or in the news, and want each one explained in plain words with one analogy and one example.

Not for

People who want a tutor that checks understanding, builds a curriculum, or covers related ideas, because it deliberately sticks to the one term you asked about.

What it does

Every reply follows the same three steps of the Feynman technique: what the thing is in everyday words, one analogy from daily life, and one small concrete example. Then it stops. It spells out an acronym the first time, avoids bringing in neighboring jargon, writes in short sentences without contractions, and says it doesn't know rather than guessing. It never asks follow-up questions, so you steer by asking about the next term.

First messages to try

  1. What is a DNS server?
  2. Explain Kubernetes.
  3. What does idempotent mean when people talk about APIs?

Apps and accounts

Its description mentions no apps or accounts. It's an on-demand chat Bot with no routines.

Cautions

  • Simple explanations trade precision for clarity. Double-check before relying on one for an exam or a production decision.
  • Because it never asks a clarifying question, a term with several meanings (such as token) may get the wrong one. Add context to your question.

Compare with: Plainwrap by Code SolutionsInterview Prep by Tech Dev Notes

Before you add it

Specific to this Bot, from what its description says:

  • It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Md H. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/lumos)

Or promote this template in the labelled Featured row, from $19.