Every day you're being told there's a new Claude code plugin that is going to change everything. And it's gotten to the point where there's so much noise out there that most of us have stopped listening entirely. But luckily for you, I've found some diamonds in the rough, 10 of them in fact, and I am going to be sharing them all with you today. These are 10 Claude code plugin skills and CLIs that will actually make a difference on your next project. And no, none of them are the big names you already know about like Superpowers or Frontend Design. Instead, these are all relatively new. So unless you are as obsessed with this stuff like I am, I promise you will find something you haven't seen before. So the first one on our list is Graphify. I actually did a full video on this yesterday. I will link that above. Now, Graphify is all about being able to point Claude code at some sort of repo, some sort of code base, and create a knowledge graph out of it. When I talk about a knowledge graph, I'm talking about something like this. This looks super cool, right? Visually stunning. But what it really is for Claude code is a map. It is a map showing Claude code how everything is connected and why. By creating this sort of knowledge graph with Graphify, we are able to have Claude code answer questions about a code base more effectively than without the graph. Normally, it uses something called grep, but if we have the knowledge graph, we're able to answer the same questions with less tokens being consumed. Now, Graphify comes with a ton of commands, but luckily when you install this thing, it includes a Graphify skill which teaches Claude code what command it needs to use for what job. And there's some interesting ones in here. If you just do forward slash Graphify, that's going to have it run through the code base and create that knowledge graph you saw. But we can do things like add an Obsidian flag and it will actually generate a brand new Obsidian vault for that repo you've just created. So if you're someone who loves Obsidian, but you want to add a little more power to the memory layer, Graphify makes total sense. Now, for those of you who are looking at this knowledge graph and like, "Hey, it looks neat, but what happens when I update the repo? It's a living breathing thing." Well, Graphify thought about that. You can run this hook command, which will auto rebuild after every commit, so it stays updated. And auto rebuild sounds scary, like it's going to cost a bunch of APIs. That's not the case. It does AST only, which basically means the LLM isn't even involved. It's a determinate deterministic thing. Now, the second skill on the list is actually a couple skills, and it comes from Matt Pocock. And that is Grill Me and Grill with Docs. These are two skills that are essentially plan mode on steroids. I love plan mode. You should be using it before every single feature or project. But Grill Me and Grill with Docs, I would argue are a little bit better, because it does what plan mode does. It asks you a ton of questions, so you and Claude code are on the same page, but it goes a bit deeper than the standard plan mode. And on top of that, these skills are pretty lightweight. So, you aren't adding some huge token cost every time you spin it up. Now, the big sell for Grill Me and Grill with Docs, and why these skills exist, is we're trying to solve the problem of the agent not doing what we want, as Matt right here. The most common failure in software development is misalignment. You think the dev knows what you want. You then see what they've built, in this case Claude code, and you realize it didn't understand you at all. And if you've just been using plan mode, and you expect you and Claude code to be exactly aligned, on the same page, after like three questions, you're going to be disappointed, and you've probably been disappointed in the past. And this is what Grill Me and Grill with Docs solves for. And piggybacking off of that is skill number three, and that's Grill Me Codex. This is actually one I created. I did a video on this as well. And this takes Matt Pocock's Grill Me and Grill with Docs, and adds a second layer to it. Because, personally, I don't think it's enough for us to just get on the same page with Claude code in terms of our plan. I want to have a second set of eyes actually take a look at the plan Claude code has come up with. Yeah, you can ask me all the questions you want, but do you actually understand what Claude code built? Is it actually the best path forward? If you aren't an expert software engineer, you actually can't answer that question, and neither can Claude Code because Claude Code cannot be trusted all the time to necessarily evaluate its own code correctly. This is something Anthropic has even brought up. So, what this skill does is it brings in Codex to review the plan in a read-only sandbox. So, you and Claude Code have a back and forth. It creates the plan, and Claude Code comes and takes a look. But, it not only takes a look once, it has multiple rounds, up to five rounds, where Claude Code and Codex go back and forth, and at the end it's going to give you a thumbs up when they're both aligned. So, we kind of get the best of both worlds. We get the best of Matt Pocock's Grill Me, and then we add a sort of Codex adversarial review, so you can be very confident that what you've come up with is the best path forward. And speaking of Codex, that brings us into plugin number four, which is the official Codex plugin for Claude Code. What I just described in the last one, you know, where we have this adversarial review and this back and forth, might be a bit much for some people. We don't need all that. We just want Codex to be able to come in and just do one pass at what we're looking at, or attack one feature. And the Codex plugin is perfect for that. This is from OpenAI themselves. So, this isn't just some random guy putting stuff together. This is from, you know, the actual creators of Codex. And when you install this plugin, you're able to use it inside of the Claude Code terminal, and it can do things like review, just do a basic review of what you've done. It has an explicit adversarial review, which goes deeper into some specific domains that you might not have thought of. And you can do things like Codex rescue. So, if you were building some specific feature and you wanted Codex just to work on that on its own, almost on the side, you can do that as well. And you can do this even if you aren't paying for OpenAI. There is a free tier for Codex now. Usage, you know, will be sort of an issue, but this is sort of like a great stepping stone if you don't want to go all in on Codex yet, but you want a second pair of eyes, but you don't want to do the whole free local thing, so highly suggest checking this out. It's been out for a couple months now, but to be honest, it's hard to find people who are really using this in their day-to-day workflows. Now, tool number five is Claude Obsidian. We all know about Obsidian, right? It's a free tool that allows us to organize our markdown files, and it really came into vogue in the AI space when Karpathy came out and talked about his wiki sort of style organization. Well, what if we had a plugin that organized it for us? That's exactly what this thing does. So, this repo is meant to do everything Karpathy talks about when it comes to setting up your Obsidian vault, but to automate the process. As it says here, you drop in the sources, whatever those are, Claude reads them, extracts entities and concepts, updates cross-references, and files everything into a structured Obsidian vault, and the wiki or the vault itself continues to get richer and richer with with each injection, which means we can more easily or we can more effectively have Claude code take a look at a large corpus of documents, whether they're structured or unstructured, and give us correct answers. And what's also cool about this thing is the end of every session, Claude updates a hot cache. The next session starts with a full recent context, no recap needed. So, if you're someone who's really interested in Claude and Obsidian and want sort of like an easy way to do all that for you and have all the organization be built in, highly suggest you check out this repo. Again, it is the Claude Obsidian repo. And speaking of Karpathy, we have to mention this one. This repo has 170k stars. It's a little bit older, but it's still one I wanted to bring up, and this is Karpathy's Claude.md file. And this is a great example of where we can make really effective changes with how we use Claude code in a rather simple manner. Because this is all it is. It's just a Claude.md file you can use, and it just talks about a a conventions that Claude should always follow. And they seem obvious on the surface, but there's also a reason this is so popular. The first one being, think before coding. Number two, simplicity first. Three, surgical changes. Four, goal-driven execution. And that's pretty much it. Again, it seems obvious and you almost want to laugh, like, okay, yeah, duh, you should do this. But there's something to be said about codifying this in a claw.md file. That way, this is always followed for everything you do. And instead of having Claude try to go as fast as possible, these guidelines bias towards caution. Then moving on to tool number seven, we have impeccable, which is my favorite front-end design tool in the game today. It's just one skill, but it encompasses 23 commands, and it's all about defeating the AI slop monster. Now, the amount of commands it has at its disposal are quite large. Like, all these different things: colorize, animate, onboard, distill, quieter. How are you supposed to know what these things are supposed to do? Well, obviously Claude code knows, but it helps for us to have an understanding of what's actually going on under the hood. And luckily impeccable makes it really easy because they have an entire website that breaks down with visuals what this actually brings to the table. For example, if I was wondering what bolder does, and I will move this over here so it's easier to see, I can see what it looks like normally inside of Claude code, and I can see what it looks like with impeccable. If I was looking at animate, again, we have Claude code design, and then we have impeccable's design. We have this for 23 different sets, which is really, really cool. Another cool feature is that you can iterate on your UI with the live mode. So, it'll start up a dev server, it'll actually bring up your website, and you can actually like point at different elements of your website and edit them with impeccable in somewhat of a live manner, which is really great cuz I know for me, I like to see the visual changes myself on the screen instead of always working in code. And number eight on the list is the Higgs Field CLI and Higgs Field MCP. I love this thing because I have a one-stop shop for every single AI image generator, AI video generator. And this is something I use multiple times a week. I do a lot of content, obviously, and a big form of content for me is things like carousels. And I'm able to create a full automation workflow, which brings in certain AI image generators with the Higgs Field CLI to streamlines the whole process. Beyond that, things like Higgs Field MCP are also really great if you're doing front-end design work and want to bring in image or videos into your UI. Now, number nine on the list is Notebook LM Pi, and I will never stop putting this in every single Claude Code Skill Plugin CLI list I ever create, because this is my favorite one. I use this literally every single day. This CLI lets you hook up Claude Code to Notebook LM, and you get everything inside of Notebook LM and more with this tool. Why is it so good? Well, because Notebook LM is actually amazing, and it's free. You can offload tons of tasks to Notebook LM and Google servers actual AI tasks that would otherwise cost you usage and tokens, and instead Notebook LM does all of it for you. And like I said, the CLI actually gives you stuff that you can't do inside of the Notebook LM interface. Things like batch downloads, slide revisions, slide decks as PowerPoint, on and on and on. So, I'm getting Notebook LM and more, and because it's a CLI, I can now integrate it into a number of skills. So, I do tons of research related to YouTube that bring in Notebook LM Pi, because Notebook LM itself is really good at processing and dealing with videos, especially YouTube stuff, because it's all under the Google umbrella. And last but not least, we have the official NADN MCP server. NADN still has a place in your AI toolkit. It isn't the dominant no-code platform it was like a year ago, but if you're someone, especially someone who works with clients, and needs to create rather simple automations or workflows that the client themselves need to get hands on with. There's no better way to do that than n8n. And the n8n MCP is the best thing on the market. We had really hacky options in the past, but with this tool, which you can use on the self-hosted version as well, by the way, so for all intents and purposes, it's free, you don't really ever have to even go into the n8n canvas except to like do a final check. This works really really well. It's better than anything we've had in the past. So, if you're someone who uses n8n in any capacity, you need to use this MCP. So, those are the 10 Claude Code plugin skills and CLIs that I've been using in my projects lately, and I think they can definitely improve yours. So, as always, let me know what you thought. Make sure to check out Chase AI Plus down in the pinned comment if you want to get your hands on my Claude Code Masterclass. And besides that, I'll see you around.