I Tried 100+ Github Repos for Claude. These 6 Are the Best

0:00 So, there are over 100,000 GitHub repos built for Claude right now. And most of them are honestly a waste of time. But, after trying and actually using more than 100 repos, I found 10 that I cannot

0:09 work without. And some of these help me finish projects 10 times faster, some save you money on tools you'd otherwise pay for every month, and some have completely replaced me in some parts of

0:17 my workflow. So, in this video, I'll show you what they are, what problem each one solves, [music] and how to use them to build something that businesses will actually pay you for. So, let's not

0:24 waste any time and just get straight into this one. Okay. So, the first repo is Hyperframes, and this is from Haygen. It's taken over a huge part of my video editing. You basically just tell Claude

0:33 what you want in natural language, and it builds the video out of HTML and animations, and Hyperframes renders a real MP4, so a real video, right on your computer. You can get captions, motion

0:42 graphics, title cards, product promos, all that kind of stuff. And then what I do is I build skills on top of Hyperframes to make things like YouTube video intros or Instagram Reels, course

0:51 videos, ads, so many things. Editing is no longer the bottleneck for me and my team. I'll literally drop in a raw clip and say, "Hey, can you add captions and a title card to this?" Or, "Can you turn

1:00 this into an Instagram Reel?" And a few minutes later, I've got a finished file. Now, you might have heard of something like Remotion, which also does this, but I've just found way more success with

1:07 Hyperframes. It's not a sponsored video at all, and I've enjoyed the experience using Hyperframes a lot. It's open source, it has no per-render fees, so it's completely free. And pretty much

1:15 any business that posts videos will pay for you to edit videos for them, like a gym that wants 20 caption clips a month or something like that. You can sell that as a monthly content package. And

1:25 you don't have to have any video editing experience to actually use these tools. Okay, so number two is one of the things that I use the most, and it's the Google Workspace CLI. It lets Claude work with

1:34 pretty much anything in your Google account, like your Drive, Gmail, Calendar, Docs, Sheets, and Slides, and it formats everything beautifully using the CLI. Now, you could obviously use

1:43 the built-in connector for Google inside of Claude, but those only work inside of the Claude desktop app. They don't cover everything. But, this is a CLI, a command-line tool. So, Claude Code,

1:51 CodeX, or any other agent that you build with can use the this And it comes with over 40 skills, so Claude already knows exactly how to use it. Now, setting this up will just take a few minutes because

2:01 you do need a Google Cloud project for the login, but then Claude can just walk you through it step-by-step. You just have to give access to the apps that you actually want to use through the CLI.

2:09 And most small businesses run on Google. So, weekly reports, invoices, follow-up emails, anything like that, you can help them automate that quicker. All right, repo number three is Apify, or it's

2:18 technically the Apify MCP server. There's a ton of data out there that Claude just cannot naturally, or natively I should have said, reach and touch. Sites like Instagram and Reddit,

2:27 they might either block it or just [music] need JavaScript to load it, so Claude basically gets back an empty page. So, Apify connects Claude to thousands of ready-made scrapers for

2:34 Instagram, TikTok, Amazon, tons of different websites. So, I'll basically just ask it, "Hey, can you find bakeries in Chicago on Instagram and give me their follower count and download the

2:43 videos and show me the ones with, you know, no websites in their bio," things like that. And then a couple minutes later, you've got a spreadsheet right there. The connector is open source, but

2:50 the scrapers run on Apify's cloud, so you might have to pay a few bucks depending on which scraper you're using. The free plan gives you five bucks of credit a month, and then the other

2:59 actors you might have to pay for, like I said, per result. There are also some other open source repos out there that help you scrape different things like Firecrawl, but Apify has been really

3:06 easy to use as well. All right, so full disclosure, this next one I built, and it's called Scrollcraft, and I'll link it in the description. You've probably seen those Apple-style websites where

3:14 you scroll and the whole page moves like a movie and it's super immersive. There's different layers. It just feels cool. And if you ask Claude for one, you usually get a very generic page with a

3:22 couple of different weird text fade-ins or something like that. Scrollcraft gives Claude a real scroll engine plus the design rules that I've picked up by building a bunch of different websites,

3:31 and it has a checker built in that screenshots the scrolls and looks at the positions, so Claude can fix things before you ever have to instruct it to fix those things. My AI automation

3:40 society site, my personal site, our event sites, every site that we build uses this repo. And what you'll notice is that not all of these sites have to be super, super scroll-driven and

3:48 immersive. The repo understands things like taste and depth, and layering, spacing, typography, color schemes. It understands just tons of great stuff for website design and for feel. Because

3:59 ultimately, the point of a website is to feel good and to be able to actually convert the user to do what you want them to do. Nowadays, with AI, a basic landing page is pretty much a commodity.

4:08 But brands that sell online still pay a designer real money for, you know, a custom scroll experience or something that's not as easy to vibe code. So, trust me, this repo is going to come in

4:16 handy when you're building your next site. Okay, now, repo number five. This is something that I found almost by accident, and it's been on every product since. It's called Humanizer, and it

4:23 makes whatever Claude writes stop sounding like AI slop. It's built on a guide that Wikipedia editors use to catch AI-generated text. So, it knows all of those like AI tells, when you can

4:34 just immediately look at it and it smells like AI. Things like not this, but that. All of those sort of setups or tee-ups. Everything coming in groups of three. Over-the-top hype words. You

4:43 basically just have to paste in website copy or the cold email that you're about to send or whatever it is, and you just tell it to humanize it using this repo. And it keeps what you were saying, but

4:51 it drops the stuff that makes people instantly scroll past or lose trust. Because obviously, copy that reads like a person wrote it is a way easier pitch than AI-generated content. Okay, so

4:59 those first five were really about landing a client. The rest of these here are more so about when a client asks you to build something real, like a cleaning company that wants customers to book

5:09 online and pay a deposit. And you've probably had this happen where you're maybe an hour or two into a build and Claude starts randomly giving you answers like it forgot everything. And

5:17 that's because long sessions get compacted or you maybe enter context rot, and details from earlier get summarized away. So, repo six fixes that. It's called Agent Skills from Addy

5:27 Osmani. Addy spent 14 years at Google and now works on Claude code at Anthropic. So, it gets the plan out of the chat and into files. You can run {slash} spec, and it writes a real spec

5:36 with you. You can run {slash} plan, which breaks it into small tasks. And then you can run {slash} build, which works through them one at a time with a check on each one. So, when a session

5:44 inevitably gets messy, you can just open up a fresh one and it can pick up right where you left off. The spec will also ask about things that you probably wouldn't think to bring up, like double

5:53 bookings or refunds or customers in different time zones. All of these edge cases that's really important to bake into your actual spec or your build. And it's something you can hand the client

6:00 before you build anything, so they know exactly what they're actually getting. That way you guys stay aligned all the way through. And if you've been using something like Superpowers from my

6:07 skills video back in May of this year, Superpowers is still really good, but Addy's is easier to follow if you're newer. And there's also other skills like Matt Pocock's, which are really

6:14 really good, especially if you're wanting to build like a developer, even if you're not a developer. So, I guess Matt Pocock's would be a bonus GitHub repo inside of this one right here. But,

6:23 let's move on to number seven, which is Expo's official skills for mobile apps. You can basically go from an idea to a real app running on your own iPhone in an afternoon, even if you're on Windows.

6:32 And they include Expo's own list of 20 things that make an app look AI-built, plus the current rules for getting into the actual app store. So, one quick tip, tell Claude to use the Expo skills by

6:42 name, because they don't always load on their own. You will also need a $99 a year Apple developer account for TestFlight or the App Store. And most shops already have something like

6:50 Square, so sell them the one workflow their current software doesn't fit. But, trust me, if you guys want to get an app into the store and you want to build it in a way that actually makes sense, this

6:58 repo's going to save you a ton of time and tons of headaches. Okay, now number eight is on the back end of that app that you're building or software that you're building with Superbase and

7:06 Stripe's official skills. So, if your app needs logins or a database or payments, which pretty much every app does need, Claude knows each company's actual security rules, like making sure

7:14 users only see their own data and checking that a payment really came from Stripe. So, only install Stripe's skill called Stripe best practices. You don't need the whole plugin to start, because

7:23 the full plugin might try to route every vendor decision through Stripe. And then you can set the Superbase connector to read only and then log in as one test user before you launch and make sure you

7:32 can't see other users' data. But, trust me, I know that the back end and the payment stuff can get very confusing. If you're vibe coder, you might get worried about some security stuff, so use these

7:40 skills. Now, number nine is what you run before you hand anything over to a client or to the the internet. Because Claude will happily tell you, "Yeah, this works." But, it might not have

7:49 actually clicked those buttons and checked if it really did work. So, Playwright CLI from Microsoft opens a real browser. It clicks through your app like a customer would, and it writes

7:57 tests that you can rerun over and over and basically just verify everything. And since it's a command line tool instead of an MCP, it doesn't dump the whole page into Claude's context. So,

8:05 it's a lot lighter on tokens as well, and it's a lot faster, honestly. So, this helps you verify and test a ton of things and find those edge cases. And then, we also have Claude Security,

8:14 which is Anthropic's security plugin. It sends a team of agents through your code looking for holes, and separate agents try to prove each other wrong, and they try to look for different findings.

8:22 >> [music] >> And you basically get a plain English report of everything that survived, and then it can write all those patches and just execute on it for you. Now, clients

8:29 don't usually care about all these tests, but what they really care about is that the booking form works and that their customer data doesn't leak. So, build this into every project. And last

8:37 but not least, we have number 10, Open SEO, because once the site or app is live, people have to find it. It plugs Claude into real keyword data, rankings, backlinks. So, instead of generic

8:46 advice, it tells you the exact page and the exact keyword where you're sitting at. Agencies use an audit like this to win the monthly SEO retainer. So, just know the free trial credits are small,

8:55 and by default, your data sits on their server unless you host it yourself. Now, some of you guys might be wondering about some of the token saving repos like Caveman or RTK, Ponytail, things

9:04 like that. Now, JetBrains actually tested all three on real coding tasks. Caveman cut about 8 and 1/2% of output tokens, where it was kind of advertising 65%. [music]

9:12 And RTK didn't really save anything, and at low effort, it made tasks more expensive. Ponytail was the only one that saved money in these tests, about 10% per task, [music] which is half of

9:22 what it advertises. And on Windows, it has an open bug that can stall every message for several seconds. So, if you want to see where your tokens actually go, a repo called Codeburn shows your

9:31 spend and flags the waste like an MCP server that you might never use, but still loads on every message. And two I recommended back in May, Claude Mem and Context Mode, I'd maybe hold off on

9:40 those for now. Claude Mem sends usage data by default, and Context Mode has an open bug that can burn through your usage. So, everything else I tested and left out will be in the description. All

9:49 right, so if you're brand new to this, don't install all of these today. I think that would be extremely overwhelming, cuz if something breaks, you might not know which repo caused it.

9:56 So, just pick the one that fixes the problem that you're currently kind of running into the most. And if you're not sure, then maybe start with the Google CLI or Appy Pie or Scroll Craft. And you

10:05 might as well start with Humanizer because that one is super super simple as well. But, pull a list of businesses with no website, you know, build one off a sample page, clean up the copy, and

10:12 then send the link. No one's going to pay you for a GitHub repo, those are free, everyone can install them. So, what you're selling is the thing that you build around it that solves their

10:20 problem. And I'll put every repo from this video inside the description of the video so that you can just go ahead and click on all of them right from there. But anyways, that is going to do it for

10:28 this one. So, if you guys enjoyed and you learned something new, please give it a like, it helps me out a ton. And as always, I appreciate you guys making it to the end of the video. I'll see you on

10:34 the next one. Peace, everyone.