AI-NATIVE ENGINEERING
You're shipping AI to production.
How many of these skills can you actually verify?
"AI engineer" is the fastest-growing job title of 2026 and nobody agrees what it means. Credentials don't prove anything. Self-assessment is noise.
This repo says — in plain language — what competent looks like at each of the 48 skills, and what weak looks like. Then it gives you the eval.
What "weak" actually looks like.
Every skill gets a one-line diagnosis. Pulled verbatim from the README.
Dumps the top 50 chunks into context and prays.
Ships to prod because "it felt right in testing."
One regex blocklist for "bad words." Blocks "Scunthorpe."
Shipped an MCP server with 30 tools named get_data_1 through get_data_30.
Pays OpenAI to answer "what is your refund policy" 4,000 times a day.
Buffers the entire response server-side, then dumps 2KB of text into the UI at once.
10 domains. 48 skills.
The full stack of what AI-native engineers ship. From foundations through governance, with nothing hand-waved.
Three ways in.
Subscribe for one skill unpacked per week.
Subscribe to the newsletter