# Empty READMEs filled with real usage across three repos

Source: https://www.michaelchurley.com/blog/empty-readme-fills-fleet  
Published: 2026-09-09  
Author: Michael C. Hurley  
Tags: follow-up, readme, content-factory, michaelmonetized, portfolio

![Empty READMEs filled with real usage](/blog/fab-analytics-same-day-php-js-ga-drop-in-json-disk/cover.png)

## Who

Operators who cloned michaelmonetized demos and found empty README stubs after packs flagged content-factory gaps.

## What

Closed six empty-README issues across three repos with real usage docs (no fake stars or metrics):

- animated-gradient-border-on-transparent-background #1+#2 via PR #3 - CSS mask border demo; install/run from package.json
- fab-analytics #1+#2 via PR #3 - PHP/JS disk analytics; honest usage
- shagent #3+#6 via PR #7 - Bun + OpenRouter + MCP CLI docs

## Where

Public michaelmonetized repos above. Paperwork in git README files, not deploys.

## When

September 8, 2026 evening ET: the three PRs merged and closed the six issues.

## Why

An empty README is a dead handoff. Real install/run copy is the minimum bar for a public demo repo.

Would you keep README fills in the next pack day sweep, or require a usage section before a repo goes public?