The locked library

🧭 How it works

Browse free. Unlock to learn.

• Guests

  See module teasers and topic pages — Connect Grok, Grok Bot, Scopes, Workflows, Troubleshoot.

• Subscribers

  Open full steps, screenshots, configs, and updates as Shopify or Grok Bot change.

🧰 Quick snippet

Credential home reminder

Safe path shape — placeholders only.

# Outside any git repo
~/.grok/shopify.env
# Windows example:
# C:\Users\<you>\.grok\shopify.env

🍆 Curriculum

All modules

1. 

   Module 1 · Locked

   🔌 Connect Grok to Shopify Admin

   Grok can run store ops only after Admin auth is right. Trap: shpss_… where Shopify expects shpat_…. MCP can list tools and still 401. Use YOUR_SHOP.myshopify.com — not a custom domain. Scope release needs merchant re-approve + often a fresh token.

   Topic page
2. 

   Module 2 · Locked

   🧰 Grok Bot + shopify.env

   Agents need a load path on disk — not secrets in chat. Durable home: ~/.grok/shopify.env with domain + shpat_…. Prefer direct Admin over MCP; Store Operator / catalog / theme bots share one file.

   Topic page
3. 

   Module 3 · Locked

   🔐 Scopes that actually matter

   401 = credential problem · 403 = missing or unapproved grant. Version release ≠ merchant approved. Inventory can work while locations still 403. Least privilege — grant the workflow pack, not the whole Admin surface.

   Topic page
4. 

   Module 4 · Locked

   🧪 Store workflows end-to-end

   Export → transform → import carefully → verify. Keep DSers Cost; retail ≈ cost×1.33; compare-at ≈ 200%; cheapest variant first. Redirect CSV ≠ product CSV. Theme/SEO via Admin API. Encarnacion = case study only.

   Topic page
5. 

   Module 5 · Locked

   🛡️ Troubleshoot & harden

   Most “MCP broken” reports are auth, scopes, or stale process. ~24h client-credentials tokens. YOUR_SHOP.myshopify.com only. Keep secrets out of chat, git, screenshots, and session zips — rotate if pasted.

   Topic page

Behind the paywall

Lessons open after checkout