All use cases

Work

NeetCode 250 → Notion tracker that fills itself

Manual solve logging dies; you want problem, pattern, difficulty, link, and last-solved date updated without typing.

Share

What hurt

Chad Baker (@thechadstack) went from nothing to a self-updating NeetCode 250 tracker in about 25 minutes with zero code. He told Grok Bot the fields in plain words (problem, pattern, difficulty, link, last solved date; auto-update; no manual logging). The bot proposed a plan; he picked Notion. It installed the Notion MCP connector (one-click authorize), pulled the full list from NeetCode’s own site data (250 problems, 18 patterns, NeetCode + LeetCode links — nothing guessed), built a “NeetCode 250 Tracker” database, loaded all 250 rows, and verified exact count with no duplicates. He signed in to NeetCode once in its browser; the bot marked 44 solves with real dates from activity history and left 17 without submissions blank instead of guessing. A routine now checks every 2 hours, marks new solves, and keeps NeetCode’s order so he can work top to bottom. Manual steps: pick Notion, connect, sign in once. Tip + workflow. Not affiliated with xAI.

What to install or create

Plain-language fields → pick Notion → MCP + site scrape → verify 250 → browser sign-in for real dates → 2-hour check routine.

Bots

  • NeetCode tracker bot

    Maintains Notion NeetCode 250 DB; marks real solves; never invents dates.

Plugins

  • Notion

    Required

  • Browser

    Optional

Files

  • Notion DB: problem, pattern, difficulty, NeetCode link, LeetCode link, last solved date.

Routines

  • Every 2 hours: check for new solves, update rows, keep NeetCode order.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read the thread https://x.com/thechadstack/status/2103641852935102860 for Chad’s five-step setup.
  2. 2Tell Grok Bot the fields in plain words: problem, pattern, difficulty, link, last solved date — auto-update, no manual logging.
  3. 3Pick Notion when it proposes a plan; authorize the Notion MCP connector in one click.
  4. 4Let it load all 250 from NeetCode’s site data and verify exact count with no duplicates before trusting the DB.
  5. 5Sign in to NeetCode once in the bot’s browser so it can mark real solve dates; leave blanks where there is no submission. Optionally schedule a 2-hour check routine.

Approval fence

Notion writes and scheduled browser checks stay behind your connect/sign-in; no guessing missing submissions.

What to tweak

Steal “fields first, verify count, never invent solve dates.” Blank beats wrong.

Source

Chad Baker @thechadstack · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro