AgentKits

ClaudeKit is the fastest path from idea to production - built on top of Claude Code - Production-ready AI subagents automate your development & marketing workflows. Build in hours, not weeks. 🤌claudekit.cc

ck:stitch is for the awkward gap between "make me a nice UI" and actual frontend code it generates a Google Stitch design, exports HTML/Tailwind + DESIGN.md, then hands a real spec to your coding agent less vibe guessing, more design-to-code handoff

most agent workflows die in the gap between "make a plan" and "ship the PR" ck:vibe is an attempt to turn that gap into a pipeline: plan, cook/fix, review, ship, then watch CI not magic just fewer places for half-done work to hide

ck:security-scan is the boring gate i want before any agent-built code ships it checks secrets, deps, and risky OWASP-style patterns with shell tools plus Claude reasoning not a pentest, just a cheap preflight before you embarrass yourself

most ai coding failures are not model failures they are context packaging failures ck:repomix turns a repo or focused module into xml/markdown/json/plain context, with token counts and secret checks before you hand it to Claude Code boring tool. huge leverage

auth is where vibe coding gets expensive ck:better-auth turns Better Auth setup into a guided Claude Code skill: email/password, OAuth, 2FA, passkeys, sessions, orgs, db adapters, migrations, rate limits less spaghetti, more control

ck:code-review turns code review into a real gate, not a vibes-based checkbox. It checks spec compliance, code quality, and red-team failure modes before claiming done. Useful when agents are too confident and humans are tired of cleaning up confident garbage.

most backend bugs are not “model mistakes” they are missing guardrails: auth, input validation, DB boundaries, tests, deploy checks ck:backend-development gives Claude Code a production API checklist instead of another vague “build backend” prompt boring skill, useful skill

most coding agents waste context before writing code ck:scout fixes the first mistake: not knowing where things live it fans out small scouts across the repo, returns the relevant files, then the main agent works with a map instead of vibes scout first, code second

agents keep getting worse at media work when every format becomes a separate tool ck:ai-multimodal turns images, audio, video, docs, tts, music, and generation into one Claude Code skill Gemini/OpenRouter/MiniMax behind one repeatable workflow

ck:use-mcp is the skill i wanted every MCP-heavy Claude Code setup to have it gives you 2 paths: - Gemini auto-routes the right tool - direct scripts run deterministic calls less tool-schema soup in context, more controlled execution

we built ck:mcp-builder for a boring reason: most MCP servers should not be 1:1 API wrappers design workflow tools, concise outputs, and errors that teach agents what to try next less endpoint plumbing, more agent leverage

this looks like a tiny Telegram fix, but it is actually one of those agent UX details that decides whether users trust the system or think it is frozen when an agent runs tools, there are three states users care about: - is it actually working? - what kind of work is happening? - will the intermediate status turn into a clean final answer? most agent products obsess over the final response that is understandable, but incomplete real workflows are not instant. the agent may search, run code, call connectors, ask another agent, wait for approval, or retry a provider if the channel does not show that lifecycle clearly, users start doing the worst possible thing: they send the same request again, refresh, interrupt the run, or assume the agent is broken GoClaw PR #139 fixes one small but important edge case in Telegram delivery: tool status updates can now lazily create a placeholder bubble when none exists, then edit that bubble, then hand it off cleanly when the final answer arrives that sounds boring until you operate agents in chat all day boring infrastructure is usually where product trust lives my take: agent UX is less about cute animations and more about state management who should care? - teams building agents inside Telegram, Slack, Discord, WhatsApp, or internal chat - founders shipping AI support or ops assistants - enterprise teams where a silent agent looks like a failed process - builders designing long-running tool workflows tradeoff: every extra status bubble can become noise if abused so the goal is not to narrate every internal thought. the goal is to expose the right operational state at the right time, without leaking tool args, secrets, or useless chain-of-thought small fix, big lesson: if your agent cannot manage intermediate states, it is not ready for serious workflows yet x.com/nlb_io/status/…

@goon_nguyen grab it here: claudekit.cc

one of the skills that takes so much of my time for optimizing, not just a simple browser use skill, but an efficient one

i've built a "vercel-for-ai-agent": the outstanding shipping experience (TOSE) our ai agents will help deploying anything anytime in seconds 💪 tose.sh

you can try our GoClaw.sh with just a few clicks now 👇

most coding agents guess when they hit a missing capability ck:find-skills does the boring better move: search the open Agent Skills ecosystem, then install the right workflow with npx skills less prompt gymnastics, more capability discovery

browser automation for agents has a context problem. ck:agent-browser uses compact accessibility-tree snapshots + stable @eN refs, so agents click/fill/screenshot without dragging full DOM dumps into context ~280 chars per snapshot vs 8K+ for Playwright MCP

Claude Code skills get more useful when they stop dumping docs into context. ck:docs-seeker turns “how do i use x?” into targeted llms.txt lookups via context7, then loads only the relevant API pages less context rot, fewer stale guesses built by ClaudeKit

most browser tests fail twice: first in product bugs, then in flaky test design ck:web-testing packages Playwright, Vitest, k6, a11y, and Core Web Vitals into one Claude Code skill the point is not more tests it is cleaner confidence gates

most people treat skills like better prompts ck:skill-creator treats them like tiny products: progressive disclosure, eval cases, benchmark loops, packaging that is the real unlock for Claude Code agents less vibes, more testable workflow