When I started coding in 2023, opening GitHub felt like walking into a machine shop.

Some dude was writing a renderer in C. Someone else was building a database engine in C++ for fun. A teenager had a compiler with three commits and a README that just said "it works."

Raw engineering. People building the layer everything else stands on.

Open it now.

Someone made a Claude skill. Someone made a marketing skill. A third person took both, put them in a folder, wrote a README, and called it a skill bundle. A fourth person bundled the bundles. A fifth made an awesome list of the bundles.

And the loop keeps going, up and up, each layer adding a license file and zero new capability.

How the loop started

Step 1: One person makes a skill. Example, a skill to write a LinkedIn post.

Step 2: Another person makes a different skill. Example, a skill to do marketing.

Step 3: A third person takes both skills and makes a bundle. Now you have a marketing bundle.

Step 4: A fourth person takes 3 bundles and makes a bundle of bundles. Now you have an all in one bundle.

Step 5: A fifth person makes a list of bundles. Now you have a list of bundles of bundles.

That is the loop. It keeps going.

Real examples of the loop right now

What it is What it holds
Superpowers A full dev method in skills, spec, plan, TDD, debugging. Over 310,000 stars
Matt Pocock skills One person publishing his own .claude/skills folder. Over 320,000 stars
Marketing skills Over 40 marketing skills in one repo. Reverse engineer marketing, cold email, SEO audit
LinkedIn skills 11 skills in one repo. Post writer, comment drafter, reply handler, humanizer, hook extractor
Bug hunter bundle 83 skills, 15 commands, 58 hunt modules in one bundle
Awesome lists Lists that link to other lists that link to other bundles

One skill is useful. A bundle can be useful. A bundle of bundles is mostly a copy of a copy.

Why it exploded

It exploded for 3 simple reasons:

  1. Easy to make. You do not need to write a full program. You write a markdown file with instructions. That is it.
  2. Easy to star. People star it to save it for later, even if they never use it. Stars go up fast.
  3. Easy to copy. You can fork a bundle, add 2 more skills, and call it a new bundle. No need to build anything new.

Real C++ work takes weeks. A skill bundle takes an afternoon. GitHub trending rewards speed, not depth. So skills win.

What is broken about the loop

The loop breaks 3 things:

  1. Trending is broken. Trending used to show new software. Now it shows new instruction folders. You have to scroll past 10 bundles to find one real program.
  2. Stars are broken. A bundle gets stars for collecting other people's work. The original builder gets less. The collector gets more.
  3. Learning is broken. New devs see bundles and think that is engineering. It is not. Engineering is building the thing the skill talks about.

The test: If you delete the bundle, does anything real break? If the answer is no, because it was just a list of other skills, then it was not a project. It was a folder of links.

Do this right now!

Open your GitHub home. Count the first 10 repos.

How many are real programs, and how many are skills, bundles, or lists of bundles?

Tell me your count in the comments. I will be down there.