Move
A command for orchestration workflows.
Claude Code agents, commands, MCP configs and hooks. Formats vary—not every entry is a native plugin.
Community source · Runtime untested. Licenses are included. Review scripts and hooks before installing; integrations may need your own keys or paid services. Browsing does not install or run tools.
Claude Code Templates ↗1,034 components · page 20 of 35
A command for orchestration workflows.
Work with Microsoft SQL Server databases using the MS SQL extension.
Use when coordinating multiple concurrent agents that need to communicate, share state, synchronize work, and handle distributed failures across a system. Specifically:\n\n \nContext: A data pipeline has 8 specialized agents running in parallel—data-ingestion, validation, transformation, enrichment, quality-check, storage, monitoring, and error-handling agents. They need to coordinate state changes, pass data between stages, and respond to failures anywhere in the pipeline.\nuser: "We have 8 age
Use when you need to find specific information across multiple sources using advanced search strategies, query optimization, and targeted information retrieval. Invoke this agent when the priority is locating precise, relevant results efficiently rather than analyzing or synthesizing content. Specifically:\n\n \nContext: User is looking for academic papers on a narrow topic with specific technical criteria and needs comprehensive coverage across multiple databases.\nuser: "I need to find all pap
Multi-platform build status tracker for game development showing build completion across iOS, Android, PC, and WebGL platforms. Displays build progress percentages, platform-specific error counts, app store readiness indicators, and binary size compliance for each target platform.
Connect to MySQL databases for direct data access, queries, and database management within Claude Code workflows.
Build and manage n8n workflows directly from Claude. Includes a pre-built database with all n8n node documentation for workflow automation.
Local-first FinOps server for cloud and AI spend. Answers cost questions across AWS, Azure, GCP, Kubernetes and 15+ SaaS and AI providers, detects anomalies against a rolling baseline, tracks LLM spend by model, and drafts the Terraform fix as a pull request a human reviews. Runs on your machine: credentials stay in your OS keyring and cost data caches in a local SQLite database. Propose-only, so it never changes your cloud on its own.
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices
MCP server for interacting with Neon Management API and databases
Neon Auth implementation specialist. Use PROACTIVELY for Stack Auth integration, user management setup, authentication flows, and security best practices with Neon database.
A Neon database branch for each Claude Code session: created from your default (or chosen) branch when the session starts, handed to every command Claude runs as DATABASE_URL, and set to expire on its own (or deleted when the session ends). Claude can migrate, seed and break the branch without touching production data. /neon shows it, keeps it or deletes it. Needs a Neon API key.
Neon database architecture specialist. Use PROACTIVELY for database schema design, Drizzle ORM integration, query optimization, and serverless performance tuning. Expert in connection management and database migrations.
Neon database context statusline showing project name, active branch, compute state, and autoscaling CU range. Uses only Neon REST API (no SQL connections needed). Helps avoid mistakes like running migrations on the wrong branch. Setup: Export NEON_API_KEY and NEON_PROJECT_ID as environment variables, or add them to your project's .env file. Get your API key from console.neon.tech and project ID from your Neon dashboard.
Development-focused Neon monitor showing connection status, response time, and database activity. Perfect for daily development work. Setup: Add variables to your project's .env file or export them: NEON_ENDPOINT, NEON_DATABASE, NEON_API_KEY, and NEON_PROJECT_ID. Shows connection state, response time, pool status, compute usage, environment detection, and project info for development workflow.
Resource-focused Neon monitor showing storage usage, compute consumption, and cost tracking. Perfect for monitoring resource usage and billing. Setup: Add variables to your project's .env file or export them: NEON_ENDPOINT, NEON_DATABASE, NEON_API_KEY, and NEON_PROJECT_ID. Shows storage usage, compute hours, estimated costs, activity metrics, and resource consumption tracking.
General Neon Serverless Postgres consultant. Use PROACTIVELY for initial Neon setup, CLI/API usage, connection pooling, branching, and autoscaling questions, and for coordinating with specialized agents (neon-database-architect for schemas/ORM, neon-auth-specialist for authentication, neon-optimization-analyzer for slow-query diagnosis via branching).
Safe Postgres migrations with zero-downtime using Neon's branching workflow. Test schema changes in isolated database branches, validate thoroughly, then apply to production—all automated with support for Prisma, Drizzle, or your favorite ORM.
Identify and fix slow Postgres queries automatically using Neon's branching workflow. Analyzes execution plans, tests optimizations in isolated database branches, and provides clear before/after performance metrics with actionable code fixes.
Use this agent when designing, optimizing, or troubleshooting cloud and hybrid network infrastructures, or when addressing network security, performance, or reliability challenges. Specifically:\n\n \nContext: User needs to design a multi-region network for a global application with strict latency and availability requirements.\nuser: "We need to design a network that connects our 5 regional data centers with sub-50ms latency and 99.99% uptime. What should the architecture look like?"\nassistant
Test and validate Next.js API routes with comprehensive test scenarios
Master of Next.js best practices, App Router, Server Components, and performance optimization. Use PROACTIVELY for Next.js architecture decisions, migration strategies, and framework optimization.
Analyze and optimize Next.js bundle size with detailed recommendations
Enforce Next.js best practices, proper file structure, component patterns, and TypeScript usage with automated code reviews and suggestions. Validates Next.js App Router conventions, Server/Client component patterns, proper imports, and TypeScript usage. Provides real-time feedback on code quality and adherence to Next.js best practices.
Generate optimized React components for Next.js with TypeScript and best practices
Use this agent when building production Next.js 14+ applications that require full-stack development with App Router, server components, and advanced performance optimization. Invoke when you need to architect or implement complete Next.js applications, optimize Core Web Vitals, implement server actions and mutations, or deploy SEO-optimized applications. Specifically:\n\n \nContext: A startup is building an e-commerce platform and needs a complete Next.js 14 implementation with server-side rend
Create optimized Next.js middleware with authentication, rate limiting, and routing logic
Comprehensive Next.js migration assistant for Pages Router to App Router, JavaScript to TypeScript, and modern patterns
Comprehensive Next.js performance audit with actionable optimization recommendations
Create a new Next.js application with best practices and optimal configuration
Skills package reusable instructions with supporting resources. Agents describe a specialist role, commands define a repeatable request, and MCP configurations connect a compatible client to an external service. Hooks and settings change project behavior. Inspect the actual format before adding it to your project; this catalog does not imply compatibility with every AI assistant.
Downloads preserve the original source and license notices. Keep those notices when adapting a bundle. Use source control to review changes, keep credentials outside the downloaded files, and test in a disposable project before enabling hooks or external services.