Composio

Composio AI

Composio AI

Composio AI

Composio AI

Composio AI

Composio AI

Composio AI

Composio AI

Composio AI

Composio AI

I tried to switch from Claude Code to OpenCode, but Claude Code still wins for me

I spent some time digging into Claude Code vs OpenCode, mostly from the angle of how they actually work as coding agents. More on the technicalities like: context and memory tool use subagents permissions safety and control study the recent leak of Claude Code model flexibility My rough take Claude Code still feels better to me for serious repo work. It is smooth, and the whole Claude-native workflow just feels really good to me. And now that Anthropic increased Claude Code usage limits after the May 6 update, I am honestly still stuck with it. OpenCode is great too, but I see it more as the tool I use when I want to try new models and providers. Stuff like Kimi K2.6, GPT, Gemini, Qwen, local models, etc. Full breakdown here: Claude Code vs. OpenCode: Technical Breakdown submitted by /u/shricodev [link] [comments]

I tested GPT-5.5 Codex against Opus 4.7 Claude Code, and it's about time Anthropic bros take pricing seriously.

I've used Claude Code the most among AI coding agents. Sonnet, Opus, I've run them all. The reason is simple: they're beasts at tool execution and prompt following. That's also why Anthropic dominates API revenue from code agents. First-mover advantage is real, and developers love them. But GPT-5.5 Codex has been insanely good. When new models drop, I run real tests, not benchmarks. This time I built two tasks: Test 1: PR triage bot – GitHub MCP, scoring formula, Slack alerts, retries, strict TS, no "any". Test 2: Real-time code review UI – React, WebSockets, optimistic rollback, virtualized diff, WS reconnect. Same prompts. Same MCP (GitHub + Slack). Same machine. Here's what I found out: Claude Code (Opus 4.7): - Verified MCP before writing a line - Built 36 files in 12 minutes - Wrote its own WebSocket smoke test (3ms broadcast) - Zero errors first run - Total cost: ~$2.50 Codex (GPT-5.5 via Cursor): - Failed Task 1 (GitHub MCP not reachable – Cursor environment issue, not model) - Task 2 shipped but needed a patch for infinite React loop - 28 files, more compact architecture - Total cost: ~$2.04 (18% cheaper) Claude shipped cleaner. Codex needed a patch pass. For complex, architecture-heavy work, I still reach for Opus – no question. But Codex was leaner, cheaper, and open source. For tight, self-contained tasks where you want to ship fast – Codex holds its own. I'm not switching. But for the first time, I'm watching the pricing gap. Full breakdown with all code, prompts, run logs, and cost tables: https://composio.dev/content/claude-code-vs-openai-codex submitted by /u/geekeek123 [link] [comments]

20 Claude Skills for Marketing, Launch and Sales built for technical people

Curated this list of 20 Claude Skills for devs to get help with marketing, sales, launch: Content human-tone: scans your copy against 18 GTM slop patterns and rewrites it. basically a linter for marketing language cook-the-blog: researches a company, extracts SEO keywords, writes a case study in MDX, generates a cover image, pushes to GitHub. one command noise-to-linkedin-carousel: paste rough notes or a voice transcript, get a carousel with hook and CTA. good for people who think faster than they write tweet-thread-from-blog: turns any blog post into a 7-10 tweet thread. optionally posts to X via Composio linkedin-post-generator: reads a GitHub PR or article, produces a post with the right hook and story arc Sales discovery: run a proper needs assessment before you pitch anything. most DevRels skip this and go straight to the demo. biggest mistake. objection-handling: "we already have something for this" and "our engineers will build it" are the two you'll hear constantly in developer sales. this is the one to internalize. storytelling: case studies and narratives move technical buyers more than feature lists. if you can make someone see themselves in a story, the sale is mostly done. qualifying-leads: not every inbound is worth chasing. knowing who to drop early saves more time than any outreach optimization. closing: DevRels are usually great at building trust and terrible at asking for the next step. this one bridges that gap. Intelligence gh-issue-to-demand-signal: give it a competitor's public GitHub repo. clusters open issues into demand categories, scores by engagement, outputs a GTM messaging brief. surprisingly useful for competitive research where-your-customer-lives: give it your ICP, it searches Reddit/HN/DuckDuckGo to find the actual communities your customers are in. per-channel entry tactics hackernews-intel: monitors HN for your keywords, Slack alert on match, no duplicates. runs on cron or GitHub Actions map-your-market: searches Reddit, HN, GitHub Issues, G2 for pain signals. outputs ICP definition and messaging angles competitor-pr-finder: finds where your competitors got covered, which journalist wrote it, and the angle that got them in. gives you a ready-to-send cold pitch Launch + Outreach show-hn-writer: drafts a Show HN post based on patterns from 250+ real HN submissions. generates 3 title variants, runs a review pass to catch anti-patterns before you post producthunt-launch-kit: taglines, listing copy, maker comment, tweet thread, LinkedIn post, 4-email sequence. all from one product description outreach-sequence-builder: buying signal in, 4-6 touchpoint sequence out across email, LinkedIn, phone cold-email-verifier: guesses, enriches, and verifies emails from a CSV autonomously npm-downloads-to-leads: give it npm package names, it pulls 12 weeks of download data, maps maintainers to GitHub/Twitter, outputs who to reach out to and what to say Link in comments 👇 submitted by /u/Sam_Tech1 [link] [comments]

I tested Kimi K2.6 vs Claude Opus 4.7 on a weird game coding task

Kimi K2.6 has been getting a lot of hype recently, mostly because it seems like a “good enough for coding, way cheaper than frontier models” option. So I wanted to test it properly. So I tested it against my favorite, Claude Opus 4.7 on a weird but practical coding task. The task was to build a small Minetest/Luanti bounty board game mod with a TypeScript backend, then extend it with Google Sheets logging through Composio. The idea is that, player joins a local world, runs /bounty, gets a task, completes it in-game, gets rewarded, and then the backend records the completion. In the second test, completions also get logged to Google Sheets. Both models got the same prompts. Setup: Claude Opus 4.7: Claude Code Kimi K2.6: OpenCode via OpenRouter Same repo, same task, same success criteria Measured: working result, code quality, debugging pain, time, token usage, and cost For pricing context, Claude Opus 4.7 costs $5/M input and $25/M output, while Kimi K2.6 is listed at $0.95/M for input tokens and $4/M for output tokens, with cached input even lower at $ 0.16/M. Test 1: local bounty board Opus 4.7 got the local version working cleanly. It built the Express/Zod/Vitest backend, Lua mod, /bounty flow, rewards, leaderboard, and tests passed. Stats: Cost: ~$3.59 Time: 12min API, 23min wall Code: +1,688 / -0 Output: 54.8k Cache read: 2.8M Pretty clean MVP. Kimi K2.6 was honestly better than I expected here. It also got the local bounty board working. Backend routes were there, Lua mod was there, and the basic game flow worked. But it felt a little messier. The annoying part was Minetest config. It wrote secure.http_mods = bountykimi in the global config, but also created a world-level config with a different mod name. So the HTTP API was not enabled for the actual mod that was running. Took me like 30+ minutes to debug because I do not play this game. Stats: Cost: ~$0.39 Duration: ~9min 27sec Code changes: +4,671 / -0 Context used: 52,073 tokens Context window used: 20% So yeah, Kimi passed Test 1. But it wrote way more code, over 2X for the same thing. Test 2: Composio + Google Sheets This is where the gap showed up. Opus 4.7 got the Google Sheets sync working. It had some issues with tsx watch and env loading, but after a bit of back and forth, the backend could complete a bounty and append it to Google Sheets through Composio. Stats: Cost: $16.03 Time: 28min API, 1hr 17min wall Code: +1,848 / -507 Cache read: 22.3M Output: 123.3k Painfully expensive, but it worked. Kimi K2.6 failed this one. It got stuck on dev server issues, tests, build problems, and never wired the Composio integration into a clean working state. After ~25 minutes and 135k+ tokens, I stopped it. Stats: Cost: ~$5.03 Time: ~25min Tokens: 135k+ Takeaway Kimi K2.6 is actually interesting for cheaper local coding tasks. For $0.39, getting a working Lua + TypeScript game mod is not bad at all. But once the task involved external tools, config issues, and real integration work, Opus 4.7 was clearly ahead. My rough verdict: Best local MVP: Opus, but Kimi is way better value Best real integration: Opus by a lot Cleaner code: Opus Cheaper experiment model: Kimi Most painful cost: definitely Opus lol I have a full breakdown with commits, screenshots, demos and the costs here: Kimi K2.6 vs. Claude Opus 4.7 in a Weird Game Coding Test Anyone else using Kimi K2.6 for real coding work? How is it holding up in a real coding workflow? Open models have not always been the best in my experience with real-world projects, but with every new model, my expectations rise a little. Let's see where Kimi K2.6 goes from here. submitted by /u/shricodev [link] [comments]

I've been using Claude Cowork since launch. Here's what actually works for non-technical tasks (no code).

I've been using Claude Cowork since it launched and most guides I found were written for developers. This one isn't. No terminal. No code. Just the stuff that actually works for normal knowledge work. What Cowork actually is Most AI tools make you do the thinking and the doing. Cowork splits that. You describe the outcome, it figures out the steps and runs them. It works on your actual local files, not uploads or copy-paste. The big difference from regular Claude chat is it can handle multi-step work without you babysitting every stage. The prompt framework that changed how I use it Every prompt needs three things: Task: clearly state what you want done Context: give it background. Who's the audience, what's the goal, what does it need to know Output: define exactly what the result should look like. Format, length, file type Then end with: "Complete this autonomously. Only stop if you genuinely need my input." That last line is what gets Cowork out of ask-permission-every-30-seconds mode and into actual execution. Skills worth setting up Skills are reusable instruction sets. You write them once, Claude follows them automatically every time. Think of them as SOPs for your AI. Email Triage: sorts unread mail into Urgent, Important, FYI, and Junk. Drafts replies for the routine ones. Never actually sends anything, just drafts. File Organizer: cleans years of folder chaos. The useful part is it shows you the full plan before moving a single file. You approve, then it runs. Meeting Notes: converts transcripts into decisions made, action items with owners, and open questions. Works retroactively on months of old transcripts too. That one surprised me. Brand Voice: feed it three writing samples plus a few rules. Everything it writes after that sounds like you, not like a LinkedIn post. Report Generator: drop a folder of messy CSVs and PDFs, describe what you need, walk away. Comes back with a formatted Word doc. I used to spend half a Friday on this. Research Synthesis: point it at a folder of competitor pages, analyst PDFs, interview transcripts. It reads all of them and gives you one integrated view, not a summary of each source separately. The setup step that makes everything better Before you run any of the above, spend 30 minutes building three context files in your workspace folder: about-me.md: your role, current projects, key stakeholders brand-voice.md: your tone, words you never use, two or three writing samples working-prefs.md: how you want Claude to behave, when to ask vs just proceed Every session after that starts with Claude already knowing your job. The quality difference between sessions with and without these files is not subtle. Skills vs Plugins (because people mix these up) A skill handles one repeatable task. A plugin bundles multiple skills into a full specialist role. So a Content Writer plugin would already know your brand voice, pull in relevant research, format everything correctly, and deliver a draft ready to publish. Anthropic ships ready-made plugins for Marketing, Legal, and Finance out of the box. Connecting Cowork to your existing tools One thing that took me a while to figure out: Cowork gets significantly more useful once you connect it to the tools you already use daily. Slack, Notion, Google Calendar, HubSpot and others can all feed context directly into your workflows so Claude isn't working blind. I've been using Composio for this part. It handles the connector layer between Cowork and external apps without any setup headache. Worth looking into once you've got the basics running. Pro tips that actually matter Run an audit first. Ask Cowork to identify where in your workflow automation would save the most time before you build anything. Schedule recurring tasks. The time savings compound fast when something runs automatically every morning. Save your best prompts as skills. If you write the same prompt twice, it should be a skill. submitted by /u/geekeek123 [link] [comments]

Persistent remote document creation/editing

I may be missing something simple here, but it seems like the biggest blindspot for Claude is the lack of a remote filesystem with read/write permissions for the documents. I know this capability exists if you want to host it yourself using Cowork/Dispatch, but it really baffles me that you can't have the same capabilities with just some kind of cloud filesystem that would have feature parity between mobile and desktop Claude apps. One of my main use cases for Claude is running research reports, and then trying to synthesize those reports into ongoing documents. Right now it's a cludge of hosting those ongoing documents on Google Drive and using the Composio MCP to modify it as I continue the research, but it seems like an obvious and trivial feature for Claude to have its own basic cloud file system (even just like 50 mb -- for my purposes at least it's just Markdown formatted text). I've queried it frequently to ask if there's a more efficient way to do this and it's always told me that this is as good as it gets. Seems like an overlooked opportunity. submitted by /u/solishu4 [link] [comments]

Top Claude skills for Opus 4.7 after cleaning up my install

Spent yesterday going through every skill I had installed because 4.7 was eating tokens way faster than 4.6 ever did and Boris said on the cache GitHub thread that people are bloating context with too many skills. Quote was something like "be selective on which agents/skills you use per project." Combined with the cache TTL switch from 1h to 5min on April 2 and the new tokenizer burning ~35% more tokens for the same prompt, every installed skill is paying rent now whether you use it or not. So I cleaned up. Started at 31 skills, ended at 10. Not because the others were bad, just because I wasn't actually using them and they were costing ~100 tokens each at startup just to scan name and description. The ones I kept and why: 1. /simplify Bundled with CC. Catches the over-engineering 4.7 loves to add (it's worse than 4.6 here, real noticeable). I run it after every feature now. 2. /debug Also bundled. Structured debugging workflow that reads the debug log instead of guessing. Way better than typing "fix this" and hoping. 3. /batch Same bundle. Decomposes big changes into worktrees. I use it for migrations now instead of letting one Claude wander 2k lines deep into a refactor. 4. skill-creator Sounds boring but the highest leverage one I have. Anytime I catch myself re-explaining the same workflow to Claude in 3 different sessions, I make a skill. Took me 10 min to make one for my commit format. Pays for itself constantly. 5. subagent-driven-development This one became basically required on 4.7 for me. Long context regressed hard, MRCR at 1m dropped from 78% to 32% vs 4.6. If you do anything non-trivial, splitting into subagents with their own contexts is the move. 6. webapp-testing Makes Claude actually run the thing end to end before claiming done. Same pattern as Boris's /go tip from his 4.7 release notes. 7. deep-research Forces it to web fetch and verify before making factual claims. Stops the fabricated "I searched and found..." nonsense that the big post yesterday was about. 8. mcp-builder Only useful if you write MCPs but if you do it's a real time saver. Saved me from shipping a broken server last week. 9. Connect (Composio) The only reason my Claude can actually create the Linear ticket and post in Slack at end of session instead of telling me "you should now go do X". Handles OAuth across ~78 saas tools, I use Linear, Slack, Notion, Gmail mostly. 10. frontend-design The official anthropic one. Install with /plugin marketplace add anthropics/skills. 277k installs on this single skill, has reason. Without it every UI Claude builds is Inter font plus purple gradient plus grid cards. ​ Most of these (4 through 9) I pulled from github.com/ComposioHQ/awesome-claude-skills. 54k stars, organized by category, the closest thing to a real curated list that exists right now. I'd been trying to write half of these myself and stopped once I realized they already existed there. The integrations side (the 78 saas thing) is the part nobody talks about enough. Stuff I dropped: a bunch of one-off review skills, two AI-coding-tool wrappers that hadn't been updated in months, three of my own old skills I'd built when I didn't really know what I was doing, and the famous frontend-design knockoffs that are just worse versions of the official one. Real test if a skill is worth keeping: did it fire and add value in the last 2 weeks? If no, uninstall. The probabilistic trigger means a skill you don't invoke explicitly mostly won't fire on its own anyway, so you're paying the install cost for nothing. Curious what others kept after the 4.7 cleanup pass. Specifically wondering if anyone has a good replacement for /simplify since it's started feeling slow on long sessions. submitted by /u/I_AM_HYLIAN [link] [comments]

Chef traveling 14 countries — need help setting up an AI agent to run my ops while I’m in the kitchen

I’m a chef on a year-long world tour (14 countries, staging at Michelin-starred restaurants) building toward opening my own restaurant in 2027. Small remote team — assistant in the Philippines, videographer, fiancée handling content. I need an AI agent that can: • Give me a daily morning briefing (calendar, email triage, top priority) • Draft and send personalized sponsor outreach emails at volume (50-100/day) • Track responses and learn which pitches work over time • Connected to Gmail, Notion, Google Calendar The catch: I’m fully nomadic. I don’t have a computer sitting somewhere running 24/7. Everything I do is from my phone or a laptop in whatever kitchen or guesthouse I’m in that week. If the best move is to set up a cheap VPS somewhere I’m open to it. What I’ve tried or looked at: • Claude Max (current daily driver, love it) • Claude Managed Agents ($0.08/hr + tokens) • Make.com + Claude API • Composio for tool connections • OpenClaw (local agent, but I don’t have a local machine running) • Tasklet • The open source “claude-chief-of-staff” repo Budget: up to $500/month for the agent infra. Main questions: 1. What’s the most reliable setup for someone who’s fully mobile with no home server? 2. Has anyone actually run Claude Managed Agents for daily ops? How stable is it? 3. Best way to do high-volume personalized email outreach without getting flagged as spam? 4. I’m not a developer — can follow instructions but not writing code from scratch. What’s realistic for me to set up? Happy to share what I build. I think a lot of solo founders and creators need something like this. submitted by /u/Lonely-Cut-9542 [link] [comments]

Best way to build an email assistant?

Hey! Now that the agent space is changing almost daily, most tutorials from 3 months ago aren't using the newest or best setups. So this question is to anyone who has built a system for managing emails automatically with the newest tools. What is your setup and would it be capable of what I want? Is Claude managed agents or claude code a good idea or would you focus on OpenClaw? Ideally the assistant would: - Sort through incoming and old emails into gmail labels/categories, e.g. on an hourly basis - Move the emails into the folders (including one for trashing later) - Ping me of any new important emails (only a few specific labels), so that I can choose to reply if needed. Ideally I would prefer the notification in channels I already use on my phone, e.g. telegram that has worked fine with openclaw. - Draft & send the reply when asked - Every morning go through my email and suggest emails I need to pay attention to, follow up on or respond to. I have a claude subscription and also an option to use openclaw (but with another model as sonnet & haiku started getting too expensive). I also use Composio for other stuff, so that could be used. I would prefer to use Claude models cause they have been the best in mimicing my writing style and if I can have this running with my Claude subscription, my wallet would be a lot happier. That's why I'm considering changing my current openclaw setup. Thanks for any input! submitted by /u/mana-aatti [link] [comments]

MCP servers not entirely working for Claude Management Agents

Managed Agents right now only accepts OAuth and Bearer Token, but many MCP servers take in x-api-key header for API Key instead of Bearer Token, such as Composio and Apollo. Could someone in charge of the development add the third support for x-api-key header for MCP as well? Thanks submitted by /u/Crazy-Sun6404 [link] [comments]

Connecting Claude Code with Composio

I've been trying to connect Claude Code with Composio but having no luck (please see screenshot below). https://preview.redd.it/17mlwom3vrtg1.png?width=1097&format=png&auto=webp&s=9817ac2a6709d3de3822ead0453ce67adc4a3d7f I have tried the following troubleshoots but it hasn't worked: Checked config file: ensured the .claude.json file isn't corrupted or empty. Cleared local cache. Updated Node.js: ensured I am using a stable LTS version. Manual MCP added via my API key. Does anyone have a step-by-step guide(s)/instructions for how to connect Composio to Claude Code, i.e. if required deleting everything and starting again (reinstalling Terminal, Python, Claude and Composio)? FYI - I'm a complete novice and had AI provide me with instructions/code to get this far (I downloaded Terminal, Python, then added Claude and Composio), albeit I got to a point where the AI was going in circles and not sure how many mistakes I've made along the way! Therefore I reckon the cleanest way would be starting from scratch as I'd also like to connect to Composio via Authenticate with OAuth rather than manually via my API key. Thanks! submitted by /u/Existing-Buffalo-403 [link] [comments]

You can now give an AI agent its own email, phone number, wallet, computer, and voice. This is what the stack looks like

I’ve been tracking the companies building primitives specifically for agents rather than humans. The pattern is becoming obvious: every capability a human employee takes for granted is getting rebuilt as an API. Here are some of the companies building for AI agents: AgentMail — agents can have email accounts AgentPhone — agents can have phone numbers Kapso — agents can have WhatsApp numbers Daytona / E2B — agents can have their own computers monid.ai — agents can read social media (X, TikTok, Reddit, LinkedIn, Amazon, Facebook) Browserbase / Browser Use / Hyperbrowser — agents can use web browsers Firecrawl — agents can crawl the web without a browser Mem0 — agents can remember things Kite / Sponge — agents can pay for things Composio — agents can use your SaaS tools Orthogonal — agents can access APIs more easily ElevenLabs / Vapi — agents can have a voice Sixtyfour — agents can search for people and companies Exa — agents can search the web (Google isn’t built for agents) What’s interesting is how quickly this came together. Not long ago, none of this really existed in a usable form. Now you can piece together an agent with identity, memory, communication, and spending in a single afternoon. Feels less like “AI tools” and more like the early version of an agent-native infrastructure stack. Curious if anyone here is actually building on top of this. What are you using? Also probably missing a bunch - drop anything I should add and I’ll keep this updated. submitted by /u/Shot_Fudge_6195 [link] [comments]

Claude Code users - how do you connect to Google Drive?

If you're a claude code user, how do you connect to google drive? Google Drive connects to claude desktop and claude.ai through a lovely cloud mcp. works great! Except google drive and a few random other cloud MCP's won't show up in claude code. There seem to be several bugs posted about it: anthropics/claude-code#32450 anthropics/claude-code#39422 anthropics/claude-code#41635 I've been asking Claude, googling like crazy, and the only thing I find are sketchy-ish github repos for google drive or Composio, which opens a whole can of worms. Google Drive MCP Integration with Claude Code | Composio submitted by /u/thebananaz [link] [comments]

Switched from MCPs to CLIs for Claude Code and honestly never going back

I went pretty hard on MCPs at first. Set up a bunch of them, thought I was doing things “the right way.” But after actually using them for a bit… it just got frustrating. Claude would mess up parameters, auth would randomly break, stuff would time out. And everything felt slower than it should be. Once I started using CLIs. Turns out Claude is genuinely excellent with them. Makes sense, it's been trained on years of shell scripts, docs, Stack Overflow answers, GitHub issues. It knows the flags, it knows the edge cases, it composes commands in ways that would take me 20 minutes to figure out. With MCPs I felt like I was constraining it. With CLIs I jactually just get out of the way. Here's what I'm actually running day to day: gh (GitHub CLI) — PRs, issues, code search, all of it. --json flag with --jq for precise output. Claude chains these beautifully. Create issue → assign → open PR → request review, etc. Ripgrep - Fast code search across large repos. Way better than grep. Claude uses it constantly to find symbols, trace usage, and navigate unfamiliar codebases. composio — Universal CLI for connecting agents to numerous tools with managed auth. Lets you access APIs, MCPs, and integrations from one interface without wiring everything yourself. stripe — Webhook testing, event triggering, log tailing. --output json makes it agent-friendly. Saved me from having to babysit payment flows manually. supabase — Local dev, DB management, edge functions. Claude knows this one really well. supabase start + a few db commands and your whole local environment is up. vercel — Deploy, env vars, domain management. Token-based auth means no browser dance. Claude just runs vercel --token $TOKEN and it works. sentry-cli — Release management, source maps, log tailing. --format json throughout. I use this for Claude to diagnose errors without me copy-pasting stack traces. neon — Postgres branch management from terminal. Underrated one. Claude can spin up a branch, test a migration, and tear it down. Huge for not wrecking prod. I've been putting together a list of CLIs that actually work well with Claude Code (structured output, non-interactive mode, API key auth, the things that matter for agents) Would love to know any other clis that you've been using in your daily workflows, or if you've built any personal tools. I will add it here. I’ve been putting together a longer list here with install + auth notes if that’s useful: https://github.com/ComposioHQ/awesome-agent-clis submitted by /u/geekeek123 [link] [comments]

I built a searchable hub for 789+ Claude Code skills and 10 autonomous AI agents — all free, open source

I've been deep in the Claude Code skills ecosystem since it launched. Every week there are new skills popping up on GitHub — PR reviewers, test generators, security scanners, database helpers — but finding the right one means digging through dozens of repos, READMEs, and awesome-lists. So I built Claude Skills Hub (clskills.in) — a single place to search, preview, and download every useful Claude Code skill. What's there right now: 789+ skill files across 71 categories (git, testing, APIs, security, DevOps, React, Python, AWS, Docker, Kubernetes, SAP, Salesforce, and 60+ more) Fuzzy search by name, tag, or category One-click download or bulk ZIP for entire collections Each skill has real, production-grade instructions — not templates or boilerplate 30+ curated collections like "Full Stack Starter", "Security Hardening", "DevOps Engineer" I also just shipped 10 autonomous AI agents. These are different from regular skills — each one chains multiple skills into a complete workflow: PR Review Agent — reads your full diff, checks for bugs, security issues, missing error handling, outputs a structured report with file:line references Test Writer Agent — finds untested code, generates tests matching your existing framework and patterns, runs them to verify Bug Fixer Agent — paste an error or stack trace, it traces through your code to root cause and proposes a minimal fix Documentation Agent — reads your actual source code and generates accurate README, JSDoc, API docs Security Audit Agent — full OWASP top 10 scan with secrets detection, dependency CVEs, injection checks Refactoring Agent — finds dead code, duplication, complexity, refactors safely with test verification after each change CI/CD Pipeline Agent — generates or debugs GitHub Actions / GitLab CI from your project structure Database Migration Agent — generates safe migrations with rollback plans and data loss checks Performance Optimizer Agent — profiles frontend bundles, backend queries, and memory usage Onboarding Agent — maps any codebase and generates a complete onboarding guide How to use any of them: Go to clskills.in/agents Click Download on any agent Drop the .md file into ~/.claude/skills/ Use it with /agent-name in Claude Code That's it. No API keys, no accounts, no setup. I also aggregated skills from several community collections: anthropics/skills (official Anthropic skills) travisvn/awesome-claude-skills ComposioHQ/awesome-claude-skills VoltAgent/awesome-agent-skills alirezarezvani/claude-skills The full source is open: github.com/Samarth0211/claude-skills-hub What's next: Custom Agent Builder — tell us your tech stack, AI generates a personalized agent for your project (live now at clskills.in/custom-agent) CLAUDE.md Generator — generates the perfect CLAUDE.md for your codebase More blog content with tutorials on how to write your own skills Continuously adding new community skills as they come out Would love feedback on what skills or agents you'd find most useful. Also open to PRs if you want to contribute skills. submitted by /u/AIMadesy [link] [comments]