๐Ÿ”ฅ Day 2 of Building in Public

Open0p Progress Update

OAuth still broken. Shipping anyway. This is the way.

๐Ÿšจ OAUTH STATUS: Still not working. We deployed a celebration page for when it does. The celebration page works perfectly. The OAuth does not. This is fine.

๐Ÿ“ฐ Breaking: Vercel Killed Claude Skills

Wait, they sunset what now?

Remember Claude Skills? That fancy retrieval system Vercel built so Claude could learn about your codebase?

Yeah, they killed it. After like... a year? Maybe less?

The replacement? A markdown file called AGENTS.md.

Just... a file. In your repo. That Claude reads.

Claude Skills

2024 - 2025
"56% of the time, agents just didn't invoke it"
โ€” Actual Vercel stats

๐Ÿ“Š The Damning Statistics

Max Success Rate
79%
Claude Skills
vs
Success Rate
100%
AGENTS.md

๐Ÿค” How Skills Failed

โ€ข 56% of the time: Agents just... didn't invoke Skills at all

โ€ข 79% max accuracy when they DID invoke it

โ€ข Sophisticated semantic retrieval, vector embeddings, the whole nine yards

โ€ข Result: A markdown file won

"Sometimes the dumbest solution outperforms sophisticated retrieval systems"

โ€” The entire AI industry, learning this lesson repeatedly

๐ŸŽฏ Why We're Laughing (and Learning)

The Lesson for MCP Tools

We spent the last 2 days optimizing our MCP tool descriptions for AI discoverability.

Trigger words. Natural language patterns. Rich error messages. Self-documenting tools.

Turns out: Making it stupid simple might be the whole game.

// Vercel's sophisticated approach: vector_embeddings + semantic_search + retrieval_augmented_generation // What actually worked: const instructions = fs.readFileSync('AGENTS.md'); // That's it. That's the whole thing.

โœ… Day 2 Actual Progress

The OAuth Situation

We built an entire celebration page for when OAuth works.

The page is live at oauth-fix-celebration-*.pages.dev

It has confetti animations and everything.

OAuth status: ๐Ÿ”ด Not working

The celebration page is more functional than the feature it celebrates.

๐Ÿง  Day 2 Wisdom

"Ship broken things. Fix them in public. The internet respects the grind."

โ€” Open0p internal memo (it's just us talking to Claude at 2am)

What we learned from Vercel killing Skills:

1. Overengineering is real and it will humble you

2. Sometimes "just read the file" beats ML pipelines

3. Ship fast, measure, kill what doesn't work

4. A markdown file with 100% success rate > fancy system with 79%

๐Ÿ”ฎ Day 3 Preview

The Plan (subject to OAuth-induced pivots)

โ€ข Fix OAuth (for real this time) (probably) (we hope)

โ€ข Test the full preview โ†’ deploy flow end-to-end

โ€ข Maybe write an AGENTS.md for our own repo (the irony)

โ€ข Continue questioning our life choices in public