/blog-post-GM — a Claude Code skill we evolved with our own Evolution engine to write every post in the Godmode voice.
Your Skill Files Are Too Long (And Claude Code Is Skipping Half)
🚨 The limit: 200 lines. After that, Claude skims or ignores your instructions.
📊 Our audit: Godmode 414 lines. One-Shot 387. Evolution 1,039. All broken.
✂️ The fix: Split into controller (<200 lines) + companion files loaded on demand
📉 Bonus: Splitting cut total content 35% — forced us to kill redundancy
LIVE 200-LINE RULER · six skill files vs. the cut · click a row to see what gets skipped
DRAG-FREE RULER · CLAUDE'S READ CEILING IS HARD AT LINE 200 — EVERYTHING RIGHT OF IT FADES.
If your SKILL.md is over 200 lines, Claude stops paying attention
to the rest. We counted every line in every Godmode skill file. The results were bad.
| Skill | Lines | Status |
|---|---|---|
| Godmode Lite | 95 | ✓ OK |
| Godmode | 414 | [ERR] 2x over |
| One-Shot | 387 | [ERR] 2x over |
| One-Shot Alpha | 418 | [ERR] 2x over |
| Evolution | 1,039 | [ERR] 5x over |
| Evo Loop | 204 | [WARN] slightly over |
The only compliant product? Godmode Lite — the free version. Our highest-tier products were the worst offenders.
Why Claude Code Skips Instructions Past 200 Lines
Skill files get loaded into Claude's working memory alongside your code, your conversation, and everything else it's juggling. The longer the file, the more likely the end of it gets ignored — at 400+ lines, you're gambling on which instructions Claude actually pays attention to.
Evolution at 1,039 lines was the worst case. Roughly 80% of its scoring rules, improvement logic, and testing steps lived past line 200 — meaning Claude probably never saw them.
How to Split Skill Files Under 200 Lines
↓
A main file (<200 lines) that tells Claude when to read each helper file
↓
Every instruction gets read. Each step gets Claude's full attention.
Think of it like a textbook: If you crammed every chapter into one page, nobody would read past the first paragraph. Splitting into chapters with a table of contents means each section gets full attention. That's what the main file + helper files pattern does for Claude.
SAME CONTENT · TWO LAYOUTS · click chapter rows on the right to flip them open
All on one page
Chapters with TOC
SAME WORDS, BETTER LAYOUT — A TOC LETS CLAUDE LOAD EACH CHAPTER FRESH.
Claude Code only automatically reads SKILL.md. But it will happily read other files in the same folder — as long as SKILL.md tells it to.
~/.claude/skills/godmode-evolution/
├── SKILL.md # Main file — 137 lines
├── scoring-engine.md # How to score — 135 lines
├── mutation-engine.md # How to improve — 145 lines
├── init-and-benchmarks.md # Setup + testing — 162 lines
└── skill-architecture.md # The 200-line rule — 94 linesEvery file under 200. Total content dropped from 1,039 to 673 lines — 35% smaller — because splitting things up forced us to cut repeated instructions we hadn't noticed.
SPLIT THE MONOLITH · click SPLIT to fission Evolution into a controller + four companions
CONTROLLER + COMPANIONS — 1,039 → 673 LINES, EVERY FILE UNDER 200.
Loading Pieces When Needed
The main file points Claude to each helper file at the exact moment it's needed:
## On `evo mutate`
1. Read `mutation-engine.md` → Follow the full mutation protocol
2. Analyze feedback logs, hypothesize, draft diff, benchmark, human gateEach step gets Claude's full attention instead of competing with every other instruction crammed into one file.
Enforcing the Limit at the Source
Evolution produces and improves skills. If it doesn't know about the 200-line limit, every skill it creates comes out as one big file. We built the limit into Evolution itself via skill-architecture.md:
- No single file exceeds 200 lines. No exceptions.
- If a skill is one big file, the first improvement is always to split it up.
- Any change that would push a file over 200 lines must include a split.
- Strict rules that can't be skipped — like minimum quality scores, delivery conditions, and loop logic — always stay in
SKILL.mdwhere Claude reads them first.
The main file holds the "what" and "when." Helper files hold the "how."
EVOLUTION FACTORY · 200-line gate at the exit · oversized files bounce & split
RULE BAKED IN AT THE SOURCE — EVERY SKILL EVOLUTION SHIPS COMES OUT < 200 LINES.
What a 2-Star Review Revealed
A 2/5 review of Godmode Lite called it "a thin motivational wrapper" that "lacks any mechanism for enforcement." They weren't wrong about Lite — but it forced a deeper question: are the paid tiers' quality controls even being read past line 200? A bad review on the free tier exposed a hidden problem in every premium product.
How to Check and Fix Your Skill Files
# Check every skill file
for f in ~/.claude/skills/*/SKILL.md; do
echo "$(wc -l < "$f") lines — $f"
done- Audit — run the script above and flag anything over 200 lines.
- Identify split points — look for separate sections or steps that don't all need to be in Claude's head at the same time.
- Extract helper files — move each section into its own
.mdfile in the same skill folder. - Wire up the main file — add a "Read
helper-file.md" instruction at the point each section is needed. - Keep strict rules in the main file — minimum quality scores, delivery conditions, and loop logic stay in
SKILL.md.
Your skills are only as good as the parts Claude actually reads. Check your line counts today.
Evolution 2.0 Ships With the Fix Built In
The updated Evolution engine enforces the 200-line split-file architecture on every skill it produces. No monoliths. No skimming. Every instruction read.
See Pricing