akiboeHow we rank
The leaderboard shows the skills people are trying to get better at right now, and how fast that is changing.
We count people, not posts
A skill moves up when more different people say they want to get better at it. One person posting ten times counts once, which is most of what keeps bots and pile-ons from steering the board.
We look for what people want to learn or improve (“how do I get better at…”, “I want to learn…”, “stuck on…”), not for everything that mentions a topic. News and adverts about a skill don’t count.
Where it comes from
Search: what people type into Google, YouTube and TikTok search when they set out to learn something (“how to get better at…”), and Google Trends where available. Attention: how often the skill’s Wikipedia article is read on phones (desktop counts are left out because crawlers inflate them). Discussion: new questions about each skill on Stack Exchange, how busy each skill’s own subreddit is, public posts on Reddit, Bluesky and Hacker News, and how many posts on X say “learn…”, “get better at…” or “improve my…” about each skill. Video: the views on new “how to” videos on YouTube and on fresh TikTok posts about each skill.
Each source is scored on its own scale first, because a busy platform shouldn’t look like a popular skill.
Rising means rising for that skill
Growth is measured against the skill’s own usual level over the previous weeks, not against other skills. Small numbers are smoothed and treated with caution, so going from 2 posts to 6 doesn’t count as a confident +200%. A single day far above a skill’s recent level is capped, so one crawler or one viral post can’t carry it. The same post copied or cross-posted counts once, one person counts for at most three skills a day, and if most of a skill’s posts come from a single community, that source is left out for the skill.
Some skills rise every year at the same time: fitness in January, study skills in September. Once we have a year of history, that seasonal rise is taken out, and those skills are labelled Seasonal rather than Exploding.
One ranking from many sources
The sources are combined by rank (reciprocal rank fusion), so no single source can carry a skill to the top on its own. Where a category has two or more sources with history, a skill needs signal from at least two of them, and a minimum number of people, before it can be ranked. While a category’s other sources are still building that history (the first weeks, or areas a source doesn’t cover), one is enough, and the board is marked “Early data”.
We rank on a cautious estimate of growth. The board doesn’t reshuffle on small changes: a skill joins at rank 20 or better and stays until it drops below 30, and a move smaller than the uncertainty in its rank is shown as “–”, not as a move.
When a source goes quiet
Sources sometimes stop answering: a provider runs out of credits, changes its terms or is down for a day. A day a source did not collect is counted as unknown, not as zero, so an outage is never read as people losing interest. A source that collected on fewer than four days in ten of a period is left out of that period, and the board names it with the last day it collected. When some days are missing, the source is compared at its rate on the days it did collect.
What learners say, and how sure we are
Skill pages also say why people learn a skill, where they get stuck, why some quit, which methods people who make progress used, and how long it took them. These come from what people write about their own learning: each person counts once per skill, and every figure shows how many people it rests on and its margin. Below 30 people, or when the margin is too wide, we show nothing rather than a guess.
Methods are compared, not crowned: a method is listed when it appears clearly more often in posts about progress than in posts about being stuck or quitting, after correcting for the many comparisons made at once. That is a sign worth knowing, not proof the method causes progress. Next to it we show what learning research says about that kind of method, where there is research.
We use three levels of claim and say which one applies. “People say”: what learners report. “Coincided with”: a change in interest lined up with an event, which may be chance. “Estimated effect”: a change measured against what similar skills did over the same time, checked against random earlier dates. We never say “because” below the third level.
Who counts as expert or early
We never claim to know what “the top 1% of people” are learning: nobody can count that honestly. Instead we name the groups we measure. Experts are advanced-practitioner communities (for example forums for experienced runners or senior developers) and highly rated answerers on Stack Exchange. We count their posts and answers, not people, and we never show or name any individual.
“Rising among experts” lists skills growing faster in that expert tier than among everyone: the expert tier’s growth minus everyone’s growth, ranked on a cautious lower bound. A skill only appears with at least 10 expert posts in the period, growth in the period before as well, and after a correction for testing many skills at once. It shows where experts’ attention is going. It is common, not causal: experts may learn something because they are already experts. The board is paused for now: in our backtest its picks went mainstream less often than chance (see “How often our early signals were right” below). We keep collecting the expert data and will bring it back if a re-run shows it beating chance.
Each skill also gets a stage, from its own two-year curve on the sources with at least eight months of history, and its size against other skills in its area. Emerging: still small for its area but growing fast and near its own high, which is where early learners are. Rising: clearly growing over the last six months. Mainstream: about as big as its area’s typical skill and holding steady. Peaked: well down from a high in the last 18 months. Seasonal: the swing follows the calendar. Some skills get no stage when the evidence is thin.
“You started this before N% of akiboe learners”
On your own goals we may show how early you started compared with other akiboe learners who have a goal on the same skill. It is counted by the date each learner started (their first goal on that skill), not by skill or progress. It only appears when at least 30 akiboe learners have that goal, it is rounded down to the nearest 5%, and it is only shown from 50% up: we never show anyone a low rank. It never compares you with people outside akiboe and never shows other learners.
If you started while the skill was marked Emerging, we say so, with how often Emerging skills went on to become mainstream within a year in our 2021–2026 backtest, next to the chance rate. Being early is not the same as being right: many Emerging skills do not take off.
You can hide these percentiles at any time from the goal card; they stay hidden everywhere. Not everyone sees them yet: we are testing whether they help people keep learning.
Top-rated players and contestants
Where a platform publishes ratings, we can name a real top group and say what it does more than everyone else. Chess: the highest-rated players on Lichess's blitz leaderboard (about 30 sampled, rated about 2800 and up). Their share of all players comes from Lichess's own published rating distribution, which counted about 710,000 weekly blitz players in October 2026, so this group is well under the top 0.01%. They are compared with 1500–1900 players drawn from recent Lichess arenas. We look at the opening families in their recent rated blitz games, counting each player once per opening.
Competitive programming: Codeforces contestants rated 2400 and up, which Codeforces puts at about the 99.2nd percentile of active rated users (Codeforces rating-distribution blog, 2026). They are compared with every other rated contestant in the same recent combined rounds (Div. 1 + Div. 2 and Global Rounds, where everyone gets the same problems), on which problem topics each person solved. So this shows where the top pull furthest ahead on the same problems, not what they chose to study. Ratios above 20× are shown as “20×+”: they mean almost only the top solve that kind of problem.
Each card shows how much more common something is among the top group (for example “2.3× as common, 95% range 1.6–3.1×”). An item needs at least 10 people in the top group and a statistically reliable difference after correcting for testing many items at once. These cards show what's common among top-rated people, not what causes their success. Individual players are never shown or stored; names are only used in memory to fetch public games and results. Cohorts refresh weekly.
What each board ranks on
Top: each source ranks skills by growth against the skill’s own usual level plus half its size, then the rankings are combined (reciprocal rank fusion). Source weights: Search and Google Trends 1.2; YouTube, TikTok, X, Reddit and YouTube/TikTok search suggestions 1.0; Bluesky, Wikipedia and subreddit activity 0.8; Hacker News and Stack Exchange 0.6. A source covering fewer than 10 skills counts in proportion.
Rising fastest: the cautious lower bound of combined growth, same weights. New: skills whose data starts in the last 90 days, ordered as Top. Fading: the largest falls, upper bound below zero. Hardest to learn: the share of people who say they are stuck, scaled by how many people that is. Rising among experts: the lower bound of expert-tier growth minus everyone’s growth (expert sources are not part of the other boards).
Privacy
Only totals are published. We don’t keep the text of posts or anyone’s name or handle (a scrambled code that changes every month is enough to count each person once), never quote individuals, and only show head-counts in broad buckets (“1k+ people”). Skills the system finds on its own appear only after a person has reviewed them, and names that touch health conditions, religion, sexuality or addiction are never put forward automatically.
Sample data
Until the first editions are scored, the board shows a sample edition, marked “Sample data”. Its numbers are illustrative and are not real rankings.
How often our early signals were right
We replayed 2021–2026 week by week, using only what was known each week, and asked: when a signal fired for a skill, did that skill go mainstream within the next year? “Mainstream” here means its Wikipedia reading entered a lasting rise. By chance, any skill in any week went mainstream within a year 16% of the time (15%–16%), so a signal is only useful if it beats that.
| Signal | Fired | Right within a year | Caught | Lead (median) | Then fell |
|---|---|---|---|---|---|
| Our “Emerging” stage label (Wikipedia) | 71 | 37%26%–48% | 10% | 11.5 wk | 25% |
| Rising among experts (expert communities vs everyone) | 30 | 7%2%–21% | 15% | 13 wk | 30% |
| Surge in the skill's own subreddit | 21 | 5%1%–23% | 11% | 5 wk | 24% |
| Hacker News surge (tech, career, money, mind) | 48 | 19%10%–32% | 19% | 28 wk | 32% |
“Fired”: times the signal flagged a skill (once per skill per half-year). “Right within a year”: share followed by the skill going mainstream, with its 95% range. “Caught”: share of skills that went mainstream that this signal had flagged in the year before. “Then fell”: share followed by a clear decline instead. Coverage: 326 skills on Wikipedia, 18 with an expert community, 16 with their own subreddit, 58 on Hacker News. One measure of “mainstream” (Wikipedia) and one period: a backtest describes the past, not the future. Run 2026-10-06.