In my first article, I built SKILLmama: an AI skill that finds, scores, and ranks the best library for your exact stack.
In my second article, I added a security gate — because a high score means nothing if the tool is dangerous.
Both of those workflows had the same assumption baked in: you already know what you're looking for.
You type /skillmama find me a job queue for Node.js and it searches, scores, and returns ranked picks. That's great when you have a specific gap in mind.
But most of the time, you don't. You're deep in building something and you haven't stopped to ask: do I have auth? do I have observability? do I have a queue? You find out the hard way — when a feature ships without rate limiting, or when something breaks and there's no error tracking.
