XBuilderLAB/cheat-on-contentPublic

You're reading this. The skill predicted it. A workflow that turns every post into a calibrated experiment—score, blind-predict, retro, evolve. The future doesn't reward effort, it rewards those who see the pattern first. 1M followers in a month — not luck, system.

AI summary: A workflow system for systematically testing, predicting, and optimizing social media content performance.

Stars
6.1K
+22 today
Forks
864
Watchers
18
Open issues
9
Open PRs
7
Contributors
~14
Commits
42
Branches
2

PythonMITCreated May 5, 2026Last push 4d ago+81 stars this week+135 this month

Star history

since May 3, 2026
02K4K6KMay 2026Jun 2026Jul 2026Aug 2026
6.1K stars as of Aug 7, 2026, tracked back to May 3, 2026. Historical curve reconstructed from public GitHub event archives, calibrated to the current total.

Signals and awards

derived from tracked data
  • Breakout launch

    6,087 stars in 94 days

  • Permissive license

    MIT

  • Continuous integration

    Automated checks passing

What cheat-on-content does

This project provides a calibrated workflow to treat content creation as a scientific experiment rather than guesswork. It implements a system where posts are scored and blind-predicted before publishing, allowing creators to run retrospectives and evolve their strategies based on actual performance. The core philosophy is to identify patterns in successful content systematically, aiming for rapid audience growth through data-driven refinement rather than relying on luck or sheer effort.

This tool is for content creators, social media managers, and marketers who want a rigorous, data-driven system for growing their audience and optimizing post performance.

  • Calibrated experiments: treats every post as a measurable test to identify successful patterns.
  • Blind prediction: forces creators to predict performance before publishing to calibrate their intuition.
  • Retrospective analysis: provides a framework for analyzing why specific posts succeeded or failed.
  • Systematic evolution: guides the continuous refinement of content strategy based on data.
  • Pattern recognition: focuses on identifying underlying structures of viral content.

Where teams use it

Accelerating audience growth

Creators can use the system to rapidly scale their following by optimizing content based on proven patterns.

Improving content intuition

By blind-predicting performance, users can align their expectations with actual audience reactions over time.

Standardizing content analysis

Teams can use the workflow to objectively evaluate content rather than relying on subjective opinions.

Testing new formats

Provides a structured way to experiment with different content styles and measure their impact.

Getting started: Review the README to understand the core workflow of scoring, predicting, and running retrospectives.

README

main branch

Cheat on Content

Cheat on Content

English  ·  简体中文

Watcha Hot List · 观猹热榜 · #1

Version   License

For content creators — a skill that turns every post into a calibrated experiment.

You're reading this. The skill predicted it.
It turns every "I feel this will go viral" into a calibrated experiment.
It took me from zero to 1M followers in a month. It said I'd write this. I did.
Your doubt — predicted too.


🎬 What it actually does

Most creators live in the same gambling loop:

Publish → Numbers come in → Learn nothing → Roll the dice again

A creator who's shipped 200 pieces is barely 10% sharper than someone who's shipped 1 — because they never kept books after each round.

Cheat on Content makes every judgment get logged, retrospected, absorbed into the next:

📊 Score → 🎯 Blind-predict → 🚀 Publish → 📈 T+3d retro → 🧬 Evolve your rubric

This isn't motivation. It's compounding — every piece you don't retro is silently eroding your ability to see yourself.

One month in = you have a hit-formula that's only yours. Three months in = you're 10× sharper than your first-day self.


🌀 Origin

I never believed in fate. Until this skill made me film a video — and predicted exactly how much traffic that video would pull.

I tried to break it. I told my audience. I hoped collective observation would collapse the wave function and shift the trajectory.

The data was accurate.

I didn't escape fate. I just moved from first-order to second-order.

If even my awakening — even my audience's observation — was already in its prediction, then right now, reading this: are you here out of curiosity, or just closing the algorithm's last move?

the creator


⚖️ How it differs from other "creator tools"

Others This
Give you "inspiration" Make your own intuition measurable
AI writes for you AI judges for you — the script stays yours
Ship 10 versions, A/B test Ship one — bet in writing, settle the books with data
Static dashboard An evolving rubric — your formula 3 months from now isn't the starting one

In a sentence: other tools help you "ship more." This helps you "judge sharper."


🤔 Can't I just use ChatGPT / DeepSeek / Doubao?

Those are general assistants — they tell everyone the same thing. You ask "will this go viral?" and the answer is fitted to global average opinion, not your channel. Ask again tomorrow — same answer. It doesn't remember you. It doesn't change because of you.

This is your own ops expert — serving only your one channel:

  • The scoring formula is reverse-engineered from your history, not the global training distribution
  • Every piece you ship updates its understanding — by month three, judgment accuracy is 10× sharper than day one (auto-evolving)
  • It knows your benchmark account, your cadence, the last three reasons you flopped — things ChatGPT forgets after the first reply

General LLMs help everyone. This helps your account.


🛡️ Why the loop actually evolves

📝 Every piece is logged: Score and prediction get written before publish, archived end-to-end. Three days later you settle accounts — you see exactly where you were sharp, where you were off. No more vague "I feel this one didn't land."

🔁 It gets sharper: Three same-direction misses in a row, the tool actively prompts you to upgrade your scoring formula. You don't have to remember — it remembers for you.

🛡️ Upgrades have a brake: Switching the formula requires re-scoring all historical samples — only released if it ranks more accurately than the old. Plus a cross-model independent audit — so you can't fool yourself.

🪒 The rubric is a workbench, not a museum: Observations refuted by data get deleted; observations absorbed into formal dimensions also get deleted. It only holds what's most useful right now.


📦 Install

git clone https://github.com/XBuilderLAB/cheat-on-content.git
cd cheat-on-content
bash install.sh

⚠️ Upgrading from v0.x? Run /cheat-migrate in your content project after git pull. The 1.3 → 1.4 migration is BREAKING for blind-channel integrity — it splits rubric_notes.md so the blind sub-agent can't leak actuals. Without migrate, blind scoring will keep flagging non_blind_warning. See CHANGELOG and migrations/1.3-to-1.4.md.

14 sub-skills are symlinked into your agent's skill directory. One install, every content project gets it.

Supported agents: Claude Code (default) · Codex (bash install.sh --codex) · Both (bash install.sh --all)

Frozen version: bash install.sh --copy / bash install.sh --codex --copy

Uninstall: bash uninstall.sh / bash uninstall.sh --codex (your content data is not touched)


🚀 First run

In your content project directory, open a skill-compatible agent and say:

初始化 cheat-on-content

(or init cheat-on-content)

Five yes/no questions complete onboarding. Strongly recommend importing a benchmark account — 5–10 samples and the tool gets an anchor immediately. Without one, your first 5 predictions land at ±50% precision.


⚡ Daily use

score this scripts/<...>.md       → grade only
start prediction scripts/<...>.md → blind prediction + decision log
shot scripts/<...>.md             → create video folder + buffer +1
shipped https://...                → buffer -1
retro videos/<...>/                → T+3d data + retrospective
status / fetch trends / find topic / bump rubric / find benchmark

Hook-aware agents auto-report buffer + pending retros + top candidates at every session start — no need to ask. Other agents: just say status.

Full workflow + sub-skill details: see SKILL.md.


📈 Star History

Star History Chart

📜 License

MIT. Commercial use, modification, closed-source integration — all fine.


Is this cheating? So was the calculator. So was Google. The future doesn't reward effort — it rewards those who see the pattern first.

You reading this line — that's predicted too.

View on GitHub

Recent activity

commits and pull requests

When work happens

weekday and hour
SunMonTueWedThuFriSat036912151821Sun 0:00 — 0 commitsSun 1:00 — 0 commitsSun 2:00 — 0 commitsSun 3:00 — 0 commitsSun 4:00 — 0 commitsSun 5:00 — 0 commitsSun 6:00 — 0 commitsSun 7:00 — 0 commitsSun 8:00 — 0 commitsSun 9:00 — 0 commitsSun 10:00 — 0 commitsSun 11:00 — 0 commitsSun 12:00 — 0 commitsSun 13:00 — 0 commitsSun 14:00 — 0 commitsSun 15:00 — 0 commitsSun 16:00 — 0 commitsSun 17:00 — 0 commitsSun 18:00 — 0 commitsSun 19:00 — 0 commitsSun 20:00 — 0 commitsSun 21:00 — 1 commitsSun 22:00 — 0 commitsSun 23:00 — 0 commitsMon 0:00 — 0 commitsMon 1:00 — 0 commitsMon 2:00 — 0 commitsMon 3:00 — 0 commitsMon 4:00 — 0 commitsMon 5:00 — 1 commitsMon 6:00 — 1 commitsMon 7:00 — 0 commitsMon 8:00 — 0 commitsMon 9:00 — 0 commitsMon 10:00 — 0 commitsMon 11:00 — 0 commitsMon 12:00 — 0 commitsMon 13:00 — 0 commitsMon 14:00 — 0 commitsMon 15:00 — 0 commitsMon 16:00 — 0 commitsMon 17:00 — 0 commitsMon 18:00 — 0 commitsMon 19:00 — 0 commitsMon 20:00 — 0 commitsMon 21:00 — 0 commitsMon 22:00 — 0 commitsMon 23:00 — 0 commitsTue 0:00 — 0 commitsTue 1:00 — 0 commitsTue 2:00 — 0 commitsTue 3:00 — 0 commitsTue 4:00 — 1 commitsTue 5:00 — 0 commitsTue 6:00 — 0 commitsTue 7:00 — 0 commitsTue 8:00 — 0 commitsTue 9:00 — 0 commitsTue 10:00 — 0 commitsTue 11:00 — 3 commitsTue 12:00 — 4 commitsTue 13:00 — 1 commitsTue 14:00 — 0 commitsTue 15:00 — 1 commitsTue 16:00 — 0 commitsTue 17:00 — 0 commitsTue 18:00 — 4 commitsTue 19:00 — 1 commitsTue 20:00 — 0 commitsTue 21:00 — 0 commitsTue 22:00 — 1 commitsTue 23:00 — 2 commitsWed 0:00 — 0 commitsWed 1:00 — 0 commitsWed 2:00 — 2 commitsWed 3:00 — 0 commitsWed 4:00 — 0 commitsWed 5:00 — 0 commitsWed 6:00 — 0 commitsWed 7:00 — 0 commitsWed 8:00 — 0 commitsWed 9:00 — 0 commitsWed 10:00 — 0 commitsWed 11:00 — 0 commitsWed 12:00 — 0 commitsWed 13:00 — 0 commitsWed 14:00 — 0 commitsWed 15:00 — 0 commitsWed 16:00 — 0 commitsWed 17:00 — 0 commitsWed 18:00 — 0 commitsWed 19:00 — 0 commitsWed 20:00 — 0 commitsWed 21:00 — 0 commitsWed 22:00 — 0 commitsWed 23:00 — 0 commitsThu 0:00 — 0 commitsThu 1:00 — 0 commitsThu 2:00 — 0 commitsThu 3:00 — 0 commitsThu 4:00 — 0 commitsThu 5:00 — 0 commitsThu 6:00 — 0 commitsThu 7:00 — 1 commitsThu 8:00 — 0 commitsThu 9:00 — 2 commitsThu 10:00 — 0 commitsThu 11:00 — 0 commitsThu 12:00 — 0 commitsThu 13:00 — 0 commitsThu 14:00 — 0 commitsThu 15:00 — 0 commitsThu 16:00 — 2 commitsThu 17:00 — 1 commitsThu 18:00 — 1 commitsThu 19:00 — 0 commitsThu 20:00 — 0 commitsThu 21:00 — 0 commitsThu 22:00 — 1 commitsThu 23:00 — 0 commitsFri 0:00 — 0 commitsFri 1:00 — 0 commitsFri 2:00 — 0 commitsFri 3:00 — 0 commitsFri 4:00 — 0 commitsFri 5:00 — 0 commitsFri 6:00 — 0 commitsFri 7:00 — 1 commitsFri 8:00 — 0 commitsFri 9:00 — 0 commitsFri 10:00 — 1 commitsFri 11:00 — 0 commitsFri 12:00 — 0 commitsFri 13:00 — 0 commitsFri 14:00 — 0 commitsFri 15:00 — 1 commitsFri 16:00 — 0 commitsFri 17:00 — 1 commitsFri 18:00 — 1 commitsFri 19:00 — 4 commitsFri 20:00 — 0 commitsFri 21:00 — 0 commitsFri 22:00 — 0 commitsFri 23:00 — 0 commitsSat 0:00 — 0 commitsSat 1:00 — 0 commitsSat 2:00 — 0 commitsSat 3:00 — 0 commitsSat 4:00 — 0 commitsSat 5:00 — 0 commitsSat 6:00 — 0 commitsSat 7:00 — 0 commitsSat 8:00 — 0 commitsSat 9:00 — 0 commitsSat 10:00 — 0 commitsSat 11:00 — 0 commitsSat 12:00 — 0 commitsSat 13:00 — 0 commitsSat 14:00 — 0 commitsSat 15:00 — 0 commitsSat 16:00 — 0 commitsSat 17:00 — 1 commitsSat 18:00 — 0 commitsSat 19:00 — 0 commitsSat 20:00 — 0 commitsSat 21:00 — 0 commitsSat 22:00 — 1 commitsSat 23:00 — 0 commits
Commit volume by weekday and hour (UTC). Larger dots mean more commits.
DateListRankStars gained
May 6, 2026daily#19+65