io.github.nekomangaorg/Neko/artisan

Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish. Use this skill to extract hardcoded styles to AppTheme, add TalkBack semantics, implement AnimatedVisibility or micro-animations, extract stateless Composables, and add @Preview annotations.

io.github.nekomangaorg/Neko/inspector

Removes app bloat, secures data, and ensures failures are visible. Use this skill to safely eliminate dead code or unused resources, secure vulnerabilities like hardcoded API keys, fix silent exceptions (empty catch blocks), convert heavy assets to WebP, and ensure logs do not contain PII.

io.github.NVIDIA-TAO/tao-skill-bank/tao-run-on-kubernetes

Kubernetes execution platform — submits TAO container jobs as single-pod k8s Jobs with NVIDIA GPU scheduling. Use when running on EKS / GKE / AKS / on-prem clusters with the NVIDIA GPU Operator installed, or when integrating TAO into an existing k8s-native ML platform.

io.github.mukul975/Anthropic-Cybersecurity-Skills/deploying-honeytokens-and-canarytokens

Plant canarytokens and honey credentials and alert on breach.

io.github.mukul975/Anthropic-Cybersecurity-Skills/testing-prompt-injection-in-rag-pipelines

Probe RAG applications for prompt injection via poisoned retrieved context and embedding manipulation.

io.github.mukul975/Anthropic-Cybersecurity-Skills/testing-for-system-prompt-leakage

Extract and defend system prompts plus embedded secrets and routing logic.

io.github.SRombauts/SQLiteCpp/sqlitecpp-build-cmake

Build SQLiteCpp with CMake. Use for CMake builds, tests, options, or build scripts.

io.github.borghei/Claude-Skills/sql-database-assistant

This skill should be used when the user asks to "optimize SQL queries", "explore database schemas", "generate migration SQL", "analyze query performance", or "document database structure".

io.github.borghei/Claude-Skills/database-designer

Database design with schema analysis, index optimization, and migration generation for PostgreSQL, MySQL, MongoDB, and DynamoDB. Use when designing schemas, optimizing queries, planning migrations, or analyzing database performance.

io.github.borghei/Claude-Skills/database-schema-designer

Design relational schemas from requirements with normalization, migrations, ERDs, RLS policies, and indexes for PostgreSQL, MySQL, and SQLite. Use when designing new features, reviewing schemas, or adding multi-tenancy.

io.github.borghei/Claude-Skills/senior-backend

Backend development with Node.js/Express/Fastify and PostgreSQL. Use when designing REST or GraphQL APIs, optimizing database queries, implementing authentication, building microservices, handling migrations, or reviewing backend code.

io.github.borghei/Claude-Skills/kubernetes-operator

Design, build, and operate Kubernetes operators. Use when extending Kubernetes with a custom controller, choosing a framework, designing CRDs, implementing reconciliation loops, or auditing an operator for anti-patterns.

io.github.borghei/Claude-Skills/docker-development

This skill should be used when the user asks to "analyze a Dockerfile", "optimize Docker layers", "validate docker-compose", "check container best practices", or "audit Docker configurations".

io.github.mizchi/skills/plan-audit

Run EXPLAIN QUERY PLAN against every query in a sqlc-style catalog and diff the plans against a baseline. Detects new full-table SCANs and TEMP B-TREE sort scans introduced by PRs. SQLite/D1-only today; engine extension noted below.

io.github.expo/skills/expo-deployment

Deploy Expo apps to production with EAS — build and submit to the iOS App Store, Google Play Store, and TestFlight, configure eas.json build and submit profiles, manage app versions and build numbers, publish App Store metadata and ASO, and deploy web bundles and API routes via EAS Hosting. Use whenever the user is preparing a production build, running eas build or eas submit, shipping to TestFlight, releasing or rolling out to the app stores, bumping version or build numbers, or setting up store listing metadata for an Expo app.

io.github.fossasia/visdom/frontend-pane-lifecycle

Build and debug pane lifecycle behavior in the React frontend. Use when adding pane actions, layout behavior, rendering updates, or pane-level interactions.

io.github.redis/RedisInsight/frontend

React/Redux frontend development patterns for RedisInsight UI: component folder structure, styled-components, hooks, named exports, barrel files, layout components, and theme usage. Use when editing any file under redisinsight/ui/**, writing or modifying React components, Redux slices, styled-components, custom hooks, or when the user mentions UI, frontend, React, Redux, or styled-components.

io.github.redis/RedisInsight/testing

Unit/integration testing standards for RedisInsight using Jest and Testing Library: test structure, the `renderComponent` helper, faker for test data, mocking patterns, and `waitFor` instead of fixed time waits. Use when writing or modifying any `*.spec.ts` or `*.spec.tsx` file, when adding component or slice tests, when debugging flaky tests, or when the user mentions jest, testing library, faker, or test patterns.

io.github.Melvynx/aiblueprint/nextjs-setup-project

Setup a complete Next.js project with TypeScript, Tailwind, shadcn/ui, TanStack Query, and theme support

io.github.Melvynx/aiblueprint/nextjs-setup-better-auth

Setup Better Auth with Email OTP authentication and shadcn/ui components in a Next.js project

io.github.Melvynx/aiblueprint/nextjs-add-prisma-db

Setup Prisma ORM with PostgreSQL in a Next.js project with schema, migrations, and seed data

io.github.facioquo/stock-indicators-dotnet/testing-standards

Testing conventions for Stock Indicators. Use for test naming (MethodName_StateUnderTest_ExpectedBehavior), FluentAssertions patterns, precision requirements, and test base class selection.

io.github.jleechanorg/claude-commands/automation-orchestration-guide

Guide PR automation and multi-agent orchestration library workflows.

io.github.jleechanorg/claude-commands/automation-output-verification

Use BEFORE running any automation loop. Requires stating the observable success output (PR, fixed test, push); rejects prediction-only loops.