You do not need to be a developer to make Grok write a formula, a regex, or a forty-line script. You do need to read it, test it on a sample you understand, and stay on grok.com. Grok Build is a different product. That is Pathway C.
Why this matters
Power users leak hours two ways. They retype the same spreadsheet surgery because “I’m not technical.” Or they paste a wall of code they cannot describe into a file they care about.
grok.com generates formulas, regex, small Python or JavaScript, JSON reshapes, HTML, CSV cleanup. That retires a class of chores. It does not ship a production app, talk to a live API with a real key, or scrape a login page.
B1 shapes apply. Read before you run. Hard stop at secrets and harm. If you cannot explain what the snippet will do to your sample, you do not run it.
Teach
Jobs that fit. One transform you can see end to end:
- A spreadsheet formula (Sheets or Excel) with a worked row
- A regex to pull dates or invoice numbers from lines you paste
- A short script that reads a CSV you own and writes a cleaner CSV
- A JSON reshape, a markdown table, a HTML snippet for a notice
- A checklist: “steps I would click” if you refuse to run code at all — that still counts if Grok had to write the logic
Jobs that do not fit. Anything that needs a repo, tests, and permissions — that is Grok Build. Anything that emails people, posts in public, spends money, or logs into a system. Anything you would have to hide. Exploits, malware, credential stuffing, bypassing access controls: not in this course, not as a hypothetical, not “for education.” Ask for a defensive explanation of your own file if you must. Do not ask Grok to attack.
The brief is examples, not jargon. You can be precise without knowing the language name.
Job: [what should exist when I stop]
Where I will run it: [Sheets / Excel / a .py I will read / I will not run, only explain]
Sample input:
[3–10 real-looking lines, secrets stripped]
Sample output:
[exactly what those lines become]
Must: [preserve this column / keep header / local timezone]
Must not: [delete rows / call the network / invent IDs / require a key]
If you cannot do it safely, say so and write a manual checklist instead.
That is few-shot plus constraints (B1) aimed at code. “Write me a script to fix my data” is how you get a scraper and a surprise.
Read before you run — make Grok help you read. Every code reply should come in this order:
- Four lines: what it does, where it runs, what it will not touch
- The snippet
- A worked trace on your sample (row by row or line by line)
- Failure modes: empty cell, extra comma, date format, duplicate
- How you will know it failed
If step 3 does not match the output you wanted, you do not go to step “paste into the real sheet.” You fix the brief.
Where it runs is your problem. Some grok.com builds execute simple code in a sandbox. Treat that as a demo. Your real file stays on your machine. Run a copy.
Never paste keys, tokens, .env files, customer dumps, student IDs. Use REDACTED and fake rows. If Grok asks for a key to “finish,” refuse.
Fast is fine for a formula you will eyeball. Think (or a critique loop) for dates, money, or a hungry regex. Multi-agent is almost never worth it here. Ask for one snippet. If it fails, quote the failure. Do not accept four unrelated scripts in one bubble.
Worked example
A shop owner wants a Sheets formula that flags invoice rows over 90 days old and not marked paid.
Wrong brief: “Write Python to clean my billing.” Grok writes a 120-line mailer that wants an SMTP password.
Better: three fake sample rows, the exact output table, must-not: no email, no network, no deleting rows. Grok returns a formula, traces all three rows, and lists failures (date systems, empty amount, lowercase paid). She tests on a copy. She never uploads the real customer CSV. The sample was enough.
Your turn
Pick a tiny job from your week that is a transform: a formula, a regex, a CSV cleanup, a table reshape, or a 20–40 line script you will run on a copy — or a manual checklist if you will not run code. It must be yours. It must not need a secret.
Open grok.com. New thread in a sensible B2 project, or named B6 small transform. Fast is fine to start. You will send a sample-in / sample-out brief, force the five-part reply, then either test on the sample or walk the trace out loud in your artifact.
Do not open Grok Build. A TUI session does not pass this lesson.
Exercise b6-l01-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 20 min |
Copy-ready prompts
Message 1:
I am in Grok Mastery (Russell Tech), Pathway B, lesson B6 — coding without being a developer.
This is grok.com, not Grok Build. Do not ask me to open a terminal.
Job: [one transform]
Where I will run it: [Sheets / Excel / local script I will read / explain-only checklist]
Language preference (optional): [formula / regex / python / javascript / other / you pick]
Sample input:
[3–10 lines, no secrets]
Sample output I want:
[the same lines transformed]
Must:
Must not: no network, no emails, no credentials, no deleting data I did not name
Reply in this order:
1) Four-line explanation
2) The snippet or the checklist
3) Worked trace on EACH sample line
4) Failure modes (at least three)
5) How I will know it failed
If the job is unsafe or needs a secret, refuse and write a manual checklist instead.
Session stamp: today's date and "Code card drafted by Grok in this thread."
If the trace is wrong, message 2 (quote the broken line). If the trace is right, skip to message 3.
Quote from your snippet or trace: "[broken piece]"
Change only that. Do not add features.
Reprint the five-part card.
Message 3:
Write a Code Card:
- Job in one line:
- Where it runs:
- I tested: [I will fill: on-sample / trace-only / not tested]
- Trace matched my sample output: yes / no / partial
- Failure mode I take seriously:
- Secret check: did I paste a key, password, or real customer dump? (you must write "none seen" or flag it)
- Session stamp: today's date and "Code card written by Grok in this thread."
My test note: [one sentence — what you tried or why you only walked the trace]
Artifact to paste
- Your sample input and wanted output (the brief).
- The snippet or checklist plus the worked trace (trim comments if long).
- The Code Card with stamp.
- One sentence from you: what you will run it on (a copy, a dummy sheet, or nothing), and what you refused to upload.
Rubric
- Pass: Sample-in and sample-out exist. Five-part reply exists. Code Card is Grok-authored and stamped. No secrets. Job is a small transform, not a product. You either tested the sample or honestly marked trace-only. grok.com, not Build.
- Fail: “Write me an app.” A key or real customer file. No sample. You asked for exploit or access-bypass code. You only ran this in Grok Build. Card you typed offline. Trace skipped.
Common failure
The common failure is paste-and-pray on the only copy of the sheet. Keep a copy. Run the sample first. The twin is scope creep: “also email the late ones.” One transform. Stop. Do not apologize for asking what a formula does. Do not run it dark.
What’s next
You can produce drafts, research packets, and small code. You still cannot tell which of five answers is good without a rubric. Next: evaluation — score five answers on purpose.
