@densancar Both would be best imo. CTR is the best direct value, but I think watch time is a very good indication on whether certain packaging is misleading on what the video fulfils
stop wasting your time
here's how you build this whole grok bot team
in 7 days:
( the block to paste is in the article )
day 1: paste the setup block, read the plan, create ROUTER + COLLECTOR
day 2: connect one platform, write https://t.co/vUenZnmdRs, load schema.sql
day 3: run https://t.co/2TUN0ofae4 by hand until it passes
day 4: add ANALYST, run outliers.sql, read the 25 rows yourself
day 5: add the queue + AUDITOR, push one handoff end to end
day 6: make the daily pull a routine, https://t.co/h8aiQakDYV in front of it
day 7: read the usage page, add OPS + DESK if you need them
raw views vs. views over the author's own median, clearly explained
raw views mostly rank how big the account is
a big account's slow tuesday still outruns a small account's best post ever
so divide by that author's median and you see how far a post beat its own normal
keep posts under 2 days old out of the baseline, they're still climbing
one row can still be luck
if the same format shows up across authors, that's a trend you can copy
hand those rows to your grok bot and make it say why each one worked
PRO TIP
tell your grok bot to go through every routine one at a time and label each one KEEP, SLOW, EVENT, CHECK or DELETE, biggest savings first
it's one of those audits you hand straight to the bot
the full prompt is in the article
this math will save you a lot of grok bot usage
the whole idea in one line:
usage = wake-ups x re-read
broken down:
- wake-ups: every reply, routine run and bot-to-bot message
- re-read: the whole chat that bot has had so far
the two multiply, so halve both and you're at a quarter
three moves do most of it:
→ routines get their own bot
→ one job per chat, with state in a file
→ check before you run
you can stop your bots lying to you by giving one of them 3 simple rules:
- run the check script first, any failure stops it there
- spot-check 5 random rows on the live url
- a live number under the last reading fails
anything else is vibes and you can skip it
if this isn't your GitHub in 2026... you're NGMI
finally hit 10k contributions in 12 months lmao
literally the only time my computer's been off for more than a day was when i went to Greece
20k next year?? 👀
these are the exact bot descriptions for the whole team
i'm giving you all 6 (for free):
a description is just what every task reads first
no more re-explaining the job every morning
no more rules scrolling away up the chat
no more bots doing each other's work
you paste one in and the bot already knows the job
4 are below, AUDITOR and DESK are in the article
change the niche details to yours