Turn your X bookmarks into a second brain with Grok Bot

What does this setup do?

After you connect X, Grok Bot reads your bookmarks, sorts them into keepers vs one-day noise vs tools you never tried, and writes one short note per keeper into Notion or Google Docs. Nothing is deleted on X unless you explicitly approve.

Who is it for?

People whose X bookmarks feel like a graveyard of posts they never open again and who want a searchable, tagged notes layer without rebuilding the list by hand.

How do you set it up?

Tools

• Grok Bot with X connector (plan limits vary)
• Notion workspace or Google Doc for the “second brain” index
• Optional: spreadsheet for batch review

Steps

1. Connect X to Grok Bot with read access first; keep delete and post permissions off until you trust the workflow.
2. Paste the prompt below into one Grok Bot chat. Ask for a read-only pass over your bookmarks. No API spend until you confirm the approach fits your plan.
3. Clear-out sort: work in batches (e.g. last 200 bookmarks). Buckets: worth rereading, only mattered that day, tools I never tried.
4. For each keeper, create one note with a two-line summary, why you likely saved it, and one tag (topic or project).
5. Run a pattern check: “What am I clearly trying to learn from these saves?”. One short paragraph.
6. Tool check on “tools I never tried”: does the product still exist, current price, and a reminder not to sign up until you choose.
7. Set a daily or weekly digest routine for new bookmarks since last run.
8. Add a “do one thing” step: pick one keeper and turn it into a single concrete task for this week so notes are not just a pile.
9. Schedule a six-month keep/drop review; instruct the Bot not to remove anything on X or in Notion until you say yes.
10. Work small batches and ask the Bot to verify tips or links still hold before you act on old saves.

X BOOKMARKS → SECOND BRAIN (read-only on X unless I approve)

Connect to my X account read-only. Do not delete, unbookmark, or post anything without my explicit yes.

Phase 1: Sort (batch of ~200 or fewer per run):
- Fetch my bookmarks you can access on my plan.
- Classify each: KEEP (worth rereading), DAY-ONLY (mattered that day), TOOL-SKIP (tool I never tried), or DUPLICATE.
- Report counts per bucket before creating notes.

Phase 2: Notes for KEEP items only:
For each KEEP bookmark, add one entry to [Notion database or Google Doc URL I provide] with:
- Title (from post or your short label)
- Two-line summary
- Why I likely saved it (one sentence)
- One tag
- Link back to the original post

Phase 3: Insight:
- Write one paragraph: "What am I clearly trying to learn from these bookmarks?"
- List TOOL-SKIP items with: still exists? current pricing if public? "Do not sign up" reminder.

Phase 4: Habit:
- Propose a weekly digest template for new bookmarks since [date].
- Pick ONE keeper and suggest a single "do this week" action so the second brain leads to action.

Rules:
- If X API credits or plan limits block a full fetch, say so and process the largest batch allowed; never invent bookmarks.
- Flag dead links and duplicates; do not remove on X until I approve.
- Six-month review: draft keep/drop suggestions only; no deletions until I confirm.

Start by telling me which access path you are using (connector vs reply flow) and any credit or limit implications you see.

Which chat tools work with this prompt?

This prompt needs routines and connectors, so it's written for:

• Grok Bot
• X

What tips make it smoother?

• Process oldest bookmarks first if you are testing cost on a credit-based plan.
• Keep X as archive; treat Notion or Docs as the searchable layer.
• Re-run pattern check quarterly. Saves drift as your interests change.

Where do the claims come from?

Summaries use public sources linked below, not independent verification. How setups are picked.

• Read @gilkmanz’s write-up (x.com)

  @gilkmanz: Organize X bookmarks on Grok plan without API fees. Plan-dependent.

• Read @DanteBorgese’s write-up (x.com)

  @DanteBorgese: “What’s the point?”. Notes vs recreating bookmarks on X.

• Read @joxegr’s write-up (x.com)

  @joxegr: Bookmarks as graveyard of unread saves.

• Read @emanueledpt’s write-up (x.com)

  @emanueledpt: Author claim: ~$0.50 to sort 99 bookmarks using X API credit.

• Read @papagatorz’s write-up (x.com)

  @papagatorz: Author claim: @bot bookmark reply flow without X API credits.

• Read @BsalehUae’s write-up (x.com)

  @BsalehUae: Work in small batches; verify tips still hold.

• Read @free_ai_guides’s write-up (x.com)

  @free_ai_guides: Format reference for bookmark-to-notes workflows.