claude-code-plugins skills

baodq97/open-plugin

Skill Claude CodeCodex

Part of design-thinking

Use this skill when the user wants to create a PRD from scratch, explore a problem space, run Design Thinking, or transform pain points into structured product requirements. Guides users through Empathize, Define, Ideate, Prototype, and PRD compilation to produce a vbounce-compatible Product Requirements Document.…

baodq97/open-plugin

Skill Claude CodeCodex

Part of profile-playbook

This skill should be used when the user asks to "define IT strategy", "create IT governance", "write an IT roadmap", "do IT leadership planning", "IT governance framework", "review my IT strategy", "CIO task", "IT portfolio", "IT operating model", "IT investment", "digital transformation", "technology strategy", "IT…

baodq97/open-plugin

Skill Claude CodeCodex

Part of vbounce

Use this skill when the user wants to run a V-Bounce SDLC cycle, start a vbounce workflow, or manage a structured software development lifecycle with the V-Bounce framework. Orchestrates 12 specialized agents through phases: Requirements, Design, Contracts, Implementation (unified TDD), Review, and Deployment with…

atretyak1985/swarmery

Skill Claude CodeCodex

Part of architecture-pack

Generate or refresh the repo-wide architecture map — architecture-out/architecture-map.json (machine contract with named flows) + architecture-map.html (self-contained viewer). Use when the user asks for an architecture map, repo map, "/architecture-map", or when an agent needs a fresh machine-readable architecture…

atretyak1985/swarmery

Skill Claude CodeCodex

Part of claude-eng-pack

Use when designing or reviewing Claude-based agent systems — agentic loops and stopreason handling, multi-agent orchestration, coordinators, subagent invocation and context passing, workflow enforcement, Agent SDK hooks (PreToolUse/PostToolUse), task decomposition, or session state and resumption. Also when an agent…

atretyak1985/swarmery

Skill Claude CodeCodex

Part of claude-eng-pack

Use when writing or reviewing system prompts, few-shot examples, structured output via tool use, JSON schema validation with retry loops, Message Batches API processing, or multi-instance/multi-pass review pipelines such as automated PR reviewers. Also when outputs are inconsistent between runs, JSON fails validation…

dinglebear-ai/cortex

Skill Claude CodeCodex

Part of cortex

This skill should be used when the user asks to "search logs", "check errors", "tail logs", "show recent logs", "find log entries", "correlate events", "list hosts", "log stats", "syslog", "check homelab logs", or mentions system logs, syslog, log analysis, or log intelligence across homelab hosts.

dinglebear-ai/cortex

Skill Claude CodeCodex

Part of cortex

This skill should be used after running cortex action=abuseinvestigate to analyze the resulting evidence bundle. Use when the user asks to assess frustration incidents, evaluate abuse signals, analyze agent or user friction, produce a frustration report, or follow up on abuseinvestigate results.

dinglebear-ai/cortex

Skill Claude CodeCodex

Part of cortex

Search and explore AI/Claude/Codex conversation history stored in cortex. Trigger when: the user asks to "search sessions", "find conversations", "what did I work on", "session history", "past conversations", "ask history", "when did I last use X", "show recent sessions", "list AI projects", "what tools have I used"…

dinglebear-ai/rarcane

Skill Claude CodeCodex

Part of rarcane

Use when the user wants to inspect or manage Arcane Docker resources through rarcane, including projects, containers, images, networks, volumes, registries, vulnerability scans, image updates, environments, system operations, or GitOps syncs.

wewpellex21/code-sensei

Skill Claude CodeCodex

Servers, routes, APIs, and backend architecture. Activated when Claude creates server-side code, API routes, or Express/Fastify/Next.js API handlers.

wewpellex21/code-sensei

Skill Claude CodeCodex

Reading errors, troubleshooting, and fixing bugs. Activated when Claude encounters errors or when the user is debugging. Teaches the most valuable skill: understanding what went wrong.

wewpellex21/code-sensei

Skill Claude CodeCodex

React, components, state management, and modern frontend concepts. Activated when Claude works with .jsx/.tsx files or React-related code. Most vibecoded apps use React.

bethanychamberlain/claude-skills-librechat

Skill Claude CodeCodex

Part of librechat-core

Use when configuring LibreChat, editing librechat.yaml, adding endpoints, setting up model providers, configuring modelSpecs, or adjusting interface settings. Also use when asked about LibreChat configuration options, YAML structure, or endpoint setup.

bethanychamberlain/claude-skills-librechat

Skill Claude CodeCodex

Part of librechat-data

Use when setting up LibreChat RAG (Retrieval-Augmented Generation), configuring embeddings providers, setting up file search in agents, configuring PGVector/PostgreSQL for vector storage, or troubleshooting document indexing and retrieval. Also use when users ask about 'chat with documents' or 'file search' features.

bethanychamberlain/claude-skills-librechat

Skill Claude CodeCodex

Part of librechat-mcp

Use when configuring MCP (Model Context Protocol) servers in LibreChat, connecting external tools via MCP, setting up mcpServers in librechat.yaml, or debugging MCP tool connections. Also use when asked about extending LibreChat agents with external capabilities through MCP.

iwritec0de/app-dev

Skill Claude CodeCodex

Part of app-dev

This skill should be used when the user asks to 'debug a JavaScript error', 'fix a TypeScript error', 'debug a React component', 'fix a Next.js error', 'debug an API route', 'fix a hydration error', 'investigate a runtime error', or mentions 'JS debugging', 'stack trace', 'React error boundary', 'hydration mismatch'…

iwritec0de/app-dev

Skill Claude CodeCodex

Part of app-dev

This skill should be used when the user asks to 'write tests', 'add test coverage', 'test a component', 'test an API route', 'test a hook', 'set up Vitest', 'use React Testing Library', 'mock an API', or mentions 'component testing', 'integration tests', 'vitest', 'RTL', 'msw', 'testing library'. Provides…

iwritec0de/app-dev

Skill Claude CodeCodex

Part of app-dev

This skill should be used when the user asks to "style a component with Tailwind", "set up dark mode", "create a responsive layout", "build a reusable UI component", "configure Tailwind", "use cn() utility", or mentions "tailwind", "tailwindcss", "utility class", "className", "dark mode", "responsive design"…

MisterClean/claude-plugins

Skill Claude CodeCodex

Part of cook-county-data-portal

This skill should be used when the user asks to "query Cook County data", "find Cook County datasets", "get property assessments", "download parcel data", "search datacatalog.cookcountyil.gov", "get medical examiner data", "find court cases", "query State's Attorney data", or mentions Cook County government data…

MisterClean/claude-plugins

Skill Claude CodeCodex

Part of gridstatus-api

This skill should be used when the user asks to "get electricity data", "query grid data", "get LMP prices", "fetch load data", "get fuel mix", "query ERCOT data", "query CAISO data", "query PJM data", "get electricity prices", "analyze grid operations", "get ISO data", or mentions electricity market data (load…

MisterClean/claude-plugins

Skill Claude CodeCodex

Part of us-census-data

This skill should be used when the user asks to "get Census data", "query American Community Survey", "find ACS data", "get population by state", "query Decennial Census", "find Census variables", "get median income data", "download demographic data", "Census API query", "get housing data from Census", or mentions US…

cukas/patrol

Skill Claude CodeCodex

Part of patrol

Use when implementing features, refactors, or multi-file changes. Orchestrated plan-then-execute with subagent dispatch and regression checkpoints.

cukas/patrol

Skill Claude CodeCodex

Part of patrol

Use when investigating a bug or unexpected behavior. Forces structured root-cause investigation before any code changes. Trace the call chain, document hypotheses, confirm the root cause, then fix.