I kept copying the same rule files into every Cursor project. Built a package manager to fix it

debug-agent.md, code-reviewer.md - same files, every time, manually.

So I built something to fix that.

pip install skillhub-ai

skillhub install debug-agent

What I found after using it for a few weeks: the value isn't just

convenience. It's consistency. When I install a skill, my Claude

agent follows the same methodology on every project - same debug

discipline, same review axes, same output format. No drift.

The thing I didn't expect to build but ended up loving: compose.

skillhub compose python-patterns security-review api-design -o fastapi-expert

It merges multiple skills into one with conflict detection. Now I

have a single /fastapi-expert command that covers Python conventions,

OWASP checks, and REST design together.

22 skills in the registry. New in v0.1.2: skillhub init my-skill

to scaffold your own. It also writes .claude/skills.json on install

so your agent can route intent without loading every skill file.

It also happens to support Cursor, Codex, and Gemini - same install

command drops the file in the right place for each. But I built it

primarily for Claude Code so that's where it's most tested.

GitHub: github.com/chandrudp29/skillhub

Docs + cookbook: github.com/chandrudp29/skillhub/blob/main/docs/cookbook.md

Happy to answer questions. What skill would be most useful to you?

WebBrain lives inside your browser and can run entirely on your own local model — no cloud, no account, no data leaving your machine.

Most "AI browser agents" are a chat box that pastes your page into someone else's server. That's not an agent that lives where you browse — and WebBrain draws a very clear line between the two.

It's an open-source (MIT), local-first browser agent for Chrome and Firefox. It runs inside your existing authenticated session, on a model you pick — so with llama.cpp or Ollama, nothing leaves your machine.

Here's what's actually interesting:

→ Two modes, cleanly separated. Ask reads the page (read-only, content scripts). Act clicks and types through the Chrome DevTools Protocol (chrome.debugger) — trusted input events that modern sites honor, reaching cross-origin iframes and shadow DOM.

→ UI-first by design. For anything that submits, sends, or buys, it drives the visible UI and refuses to hit REST/GraphQL endpoints directly. It starts read-only and asks before consequential actions.

→ Bring any model. llama.cpp, Ollama, LM Studio, vLLM — or OpenAI, Claude, Gemini, DeepSeek, Groq, OpenRouter. Recommended local: Qwen 3.6 35B (Qwen3.6-35B-A3B), which beat Gemma 4 on the project's screenshot benchmark.

→ Tuned for cost and privacy. Token-conscious screenshots, oldest-first context trimming, a dedicated vision model, 40+ tools (~20 in Compact mode). No telemetry. No accounts.

Full analysis: https://www.marktechpost.com/2026/07/02/meet-webbrain-an-open-source-local-first-ai-browser-agent-that-reads-pages-and-automates-tasks-in-chrome-and-firefox/

GitHub Repo: https://pxllnk.co/wdva98c

Chrome Extension: https://pxllnk.co/p4mn8

Firefox Add-on: https://pxllnk.co/m6k7c5w9

Portal: https://pxllnk.co/rlifl7h

source: https://www.economist.com/briefing/2026/06/14/donald-trumps-blocking-of-anthropic-is-capricious-and-chaotic

Anthropic's Claude Cowork is one of the best AI agents you can use to get things done on your computer. Claude Cowork is an AI agent for non-technical professionals who want to automate their tasks and get polished deliverables. Claude Cowork is a very capable AI agent that can connect to a folder and have it complete tasks on your computer efficiently. However, what if you need to extract information and complete research? That is where you can use Claude for Chrome.

Claude for Chrome is the underrated Claude AI agent that not many people talk about. Claude for Chrome can navigate, click, fill forms, and complete web research in your browser. Now, you might have a question. How to use Claude Cowork with Claude for Chrome? Basically, you can trigger Claude for Chrome from Cowork, let it perform web research, and then pass the information to Claude Cowork, which can then turn it into a document, Excel, or PowerPoint file.

↗️ Full read: https://aitoolsclub.com/claude-cowork-claude-for-chrome-this-is-the-best-way-to-automate-your-workflow/

I had to analyze requests manually, so I made a workflow with n8n, Telegram, and Groq agents. Now it's all automated and logged to Google Sheets.

More automations: Join our community: https://go.phonezait.de/