Loading video...

Video Failed to Load

Go Home

Here is why Nimble has 1.1M Claude plugin installations. Ask Claude what your competitor's pricing looks like right now and it will tell you it can't browse the web. Install the Nimble skill and ask the same question. You get live, structured data back in seconds. That's the whole...

61,011 views • 2 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I just built a plugin with Claude Fable 5 that turns Claude Code into a $5,000/mo SEO consultant 🤯 9 skills, one plugin: it connects straight to your Search Console + GA4 data, finds the wins, ships the fixes, and renders a live SEO dashboard that looks like a $200/mo SaaS product. All inside Claude Code. Perfect for DTC brands and agencies sitting on months of Search Console data nobody has time to read. Right now, you probably can't answer: Which keywords are sitting on page 2, one title tag away from page 1, Which pages are bleeding traffic to redirect chains and broken canonicals, Which blog posts rank for commercial terms but never link to a product page. This plugin answers all of it from your live data, then ships the fixes: → Finds your page-2 keywords and ships the fix: new title, headings, content, paste-ready → Clusters every query into a hub-and-spoke content map with the gaps flagged → Drafts posts from your actual search data, not guesses → Writes dev tickets for redirect chains and slow pages, ranked by traffic at risk → Builds the internal links between your blog and your money pages → Flags toxic backlinks and ranks outreach targets → Drops a Monday report with 3 priorities before the client even asks → Renders it all as a one-file HTML dashboard with a 0-100 SEO health score No dashboard staring. No CSV archaeology. No $5K/mo retainer for a PDF. What you get: → Page-2 keywords moved to page 1 → A content calendar that fills itself from data → Dev tickets that write themselves → A live SEO dashboard on command Built 100% in Claude Code with Claude Fable 5. I put the entire build into a step-by-step Playbook: all 8 workflow prompts (including the dashboard), how to turn them into a plugin, and the full Google setup (Including the 2 landmines Google doesn't tell you about). Want access for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

79,880 views • 1 month ago

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 views • 1 month ago