Skills
98,639 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Safely identify and remove dead code with test verification at every step. Use when Codex needs to clean unused exports, files, dependencies, helpers, wrappers, re-exports, or duplicate code without risking regressions. Trigger for dead-code cleanup, unused dependency audits, stale utility removal, cleanup refactors, or requests to reduce code safely before or alongside maintenance work.
Package a codebase into a compact, structured context bundle for an AI agent. Use when the user wants to "give the whole repo to an LLM", "pack the codebase", hits context limits sharing a project, or asks for a digest/summary of an unfamiliar repo.
This skill should be used when bootstrapping, auditing, or reviewing the community-health and repository-cornerstone files in a code repository: README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT, issue / PR templates, CODEOWNERS, FUNDING, CITATION, and REUSE / SPDX metadata. PROACTIVELY activate on "set up new repo docs", "community health files", "what should my README contain", "do I need a code of conduct", "audit repo bootstrap docs", "repository documentation cornerstones", "pick a license", "CONTRIBUTING.md", "SECURITY.md", "vulnerability reporting", "SUPPORT.md", "CODEOWNERS", "issue templates", "PR templates", "CITATION.cff", "REUSE", "SPDX headers", "Standard Readme", "Contributor Covenant". Provides: four-question diagnostic per cornerstone, Standard Readme structure, license routing (no picking), CONTRIBUTING / CODE_OF_CONDUCT / SECURITY / SUPPORT canons, template files, and REUSE 3.3 / SPDX routing.
Responsive web design sub-skill. Provides mobile-first layout patterns, CSS Grid/Flexbox strategies, responsive images, fluid typography, container queries, and breakpoint systems. Pull this in whenever building or reviewing UI that must work across mobile, tablet, desktop, and large screens. Triggers on: "make it responsive", "responsive design", "mobile-first", "breakpoints", "fluid layout", or any request involving cross-device layout.
Migrate Riverpod from StateNotifier to Notifier/AsyncNotifier, from ChangeNotifier to AsyncNotifier, or upgrade from 0.13/0.14/1.0; ref.onDispose, family, lifecycle, riverpod migrate CLI. Use when the user asks about migrating from StateNotifier, from ChangeNotifier, upgrading Riverpod 0.13 to 0.14, 0.14 to 1.0, or Riverpod migration guides.
Provides comprehensive guidance for Rspack bundler including configuration, plugins, loaders, optimization, and Webpack compatibility. Use when the user asks about Rspack, needs to configure Rspack, optimize build performance, or migrate from Webpack.
Sa-Token integration extension skill. Covers JWT integration (comparison table of Simple/Mixin/Stateless modes), Redis persistence (JDK serialization/JSON serialization), Alone-Redis standalone Redis (isolating auth cache from business cache), AOP annotation-based authorization (using annotations in the Service layer), SpEL expression annotations (@SaCheckEL), Quick-Login quick login (zero-code login page), JSON serialization extensions (Jackson/Fastjson/Fastjson2/Snack3), template engine integration (Thymeleaf/Freemarker tag dialects), and RPC integration (Dubbo/Dubbo3/gRPC context propagation). Use when users need to integrate JWT for stateless authentication, configure Redis distributed sessions, isolate caches, use annotation-based authorization in the Service layer, or quickly build a login page. For basic login authentication, use the sa-token skill first.
Sa-Token microservice authentication skill. Covers the Same-Token mechanism for isolating internal services from the public network, unified authentication at the SpringCloud Gateway (Reactor reactive), authentication for internal RPC calls via Feign/Dubbo/gRPC, distributed Session schemes (Redis Session center / stateless JWT), Reactor/WebFlux framework integration, and SpringBoot3/4 dependency adaptation. Use when the user needs service-to-service authentication in a microservice architecture, gateway Token forwarding and validation, isolation of internal services from the public network, or distributed session sharing. For basic login authentication, use the sa-token skill first.
Sa-Token OAuth2.0 server-side skill. Covers the four grant types: Authorization Code, Implicit, Password, and Client Credentials. Includes complete OAuth2-Server setup, the SaOAuth2DataLoader data loader, custom and tiered Scope permissions, the OIDC protocol, OpenId/UnionId, custom grant_type, custom login authorization pages, annotation-based Access-Token validation, interoperability with login sessions, Scope level control, and custom API routes. Use when the user needs to build an OAuth2.0 authentication server, develop an open platform, or implement third-party application authorization. For basic login authentication, use the sa-token skill first.
Machine learning in Python with scikit-learn. Use for supervised learning (classification, regression), unsupervised learning (clustering, dimensionality reduction), model evaluation, hyperparameter tuning, preprocessing, or building ML pipelines. Provides comprehensive reference documentation for algorithms, preprocessing techniques, pipelines, and best practices.
Validates the user's environment for SageMaker AI operations — checks SDK version, AWS region, and execution role. Use when the user says "set up", "getting started", "check my environment", "configure SDK", or as the first step in any plan involving SageMaker/Bedrock training, evaluation, or deployment.
Debug and fix a Sentry issue — find it (by link, ID, or search), pull full context (stack trace, breadcrumbs, trace, logs), optionally run Seer root-cause / autofix, apply the code fix, and resolve it via a `Fixes PROJECT-NAME-12A` commit/PR. Use when working a known error or hunting one down to fix.
Orchestrates the full Sherpy planning workflow from requirements to QA-ready delivery plan. Supports AI, human, and hybrid audience selection for appropriate task detail levels. Detects which artifacts already exist, shows a visual pipeline status, and guides through each skill in sequence — gap analysis, business interview, technical interview, implementation planning, plan review, definition of done, architecture decisions, delivery timeline, QA test plan, and summary generation. Automatically organizes all artifacts into a structured docs/ folder.
Design, implement, review, or repair database schemas, queries, indexes, transactions, migrations, and backfills with explicit integrity and rollout constraints. Use when datastore behavior or the data lifecycle is a primary part of the task. Do not use for routine persistence calls whose schema and consistency contracts are unchanged.
Create, reconstruct, synchronize, or automatically record durable repository documentation and curated implementation memory from current code, configuration, tests, accepted user intent, existing docs, and Git history. Use for project context, architecture, decisions, implementation change records, timelines, build and distribution guides, maintenance handoffs, or cross-session continuity. After verified material implementation work, record the outcome by default unless the user explicitly opts out. Do not use for incidental comments, raw prompt archiving, or non-material edits.
Design, implement, or repair responsive web and app layouts across narrow, wide, zoomed, and touch-oriented viewports. Use for mobile and desktop composition variants, reflow, overflow, adaptive navigation, content-driven breakpoints, and mobile interaction layout. Do not use for purely visual styling with no responsive impact.
Svelte CLI (sv) skill. Use when the user creates a project with sv (sv create), adds integrations (sv add, e.g. drizzle/tailwind/prettier/eslint/playwright/storybook/vitest/mdsvex/paraglide/better-auth/sveltekit-adapter/mcp/experimental), runs type and compile checks (sv check), runs migration scripts (sv migrate svelte-5/sveltekit-2/app-state/self-closing-tags/package/routes), or develops a custom sv add-on.
SvelteKit advanced features guide - state management, Remote Functions, environment variables, Hooks, error handling, link options, Service Workers, server modules, snapshots (snapshots/Shallow Routing), $app/* modules, $lib, $service-worker.
Sincroniza este repositório com um novo release do upstream (mattpocock/skills), adaptando as mudanças para pt-BR em vez de copiá-las. Use quando sair um release novo no upstream ou quando uma issue de "Sync upstream" for aberta pelo workflow check-upstream.
Use this skill when users need to apply themes, customize appearance, switch dark mode, use CSS variables, configure icons, or modify visual styling for Syncfusion JavaScript controls. Covers icon library, size modes, and Theme Studio integration.
Server-state guidance for queries, mutations, caching, optimistic updates, SSR, persistence, testing, and all official adapters. Use when a project uses TanStack Query or when the task needs its setup, implementation, debugging, testing, migration, or integration guidance.
Use when integrating or debugging tiun — the web SDK (@tiun/sdk) or the React Native SDK (@tiun/react-native-sdk) — for authentication, subscription billing, one-time purchases, and time-based paywalls. Triggers on imports of `@tiun/sdk` or `@tiun/react-native-sdk`, calls like `tiun.init`, `tiun.checkout`, `tiun.login`, `tiun.start`, `TiunProvider`, `useTiun`, `useTiunEvent`, or questions about tiun products, entitlements, one-time purchases, lifetime access, fixed fees, time-based sessions, checkout return deep links, or server-side verification.
Decide something inside TypeScript or JavaScript: what a value may be and what happens when it is absent, what a failure means and who handles it, what crosses a module or service boundary, what runs concurrently and who owns the promise, what a test actually proves, what a compiler or lint setting buys. Use when the user says "is this type right", "should this throw or return", "why is this any", "how do I test this", "this promise is never awaited", "fix these type errors", or hands over TypeScript to write, review or repair. Routes to one of nine topic indexes, each owning rules that carry a decision, the conditions that trigger it, and a check. Not for prose, formatting-only passes, history questions that merely mention TypeScript, or explaining an error when the request forbids changing code.
Unity 6 audio system guide. Use when working with sound effects, music, AudioSource, AudioClip, AudioListener, Audio Mixer, spatial audio, or audio optimization. Covers 3D sound, mixer groups, snapshots, and audio import settings. Based on Unity 6.3 LTS documentation.
Detect and resolve Unity C# compilation errors using VSCode diagnostics. Use this skill when Unity projects have compilation errors that need diagnosis and automated fixes. Analyzes errors from VSCode Language Server, proposes solutions based on error patterns, and handles version control conflicts for Unity projects.
Vector database implementation for AI/ML applications, semantic search, and RAG systems. Use when building chatbots, search engines, recommendation systems, or similarity-based retrieval. Covers Qdrant (primary), Pinecone, Milvus, pgvector, Chroma, embedding generation (OpenAI, Voyage, Cohere), chunking strategies, and hybrid search patterns.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
Turn minified, bundled, or transpiled JavaScript back into readable modules. Use when you encounter unreadable production JS — a webpack/esbuild/Metro/Rollup bundle, a minified vendor script, Babel/TypeScript/SWC-transpiled output, or a single mangled .js file — and need to read, audit, debug it, or recover a best-effort SFC artifact from compiled Vue 3 component code. Not a deobfuscator.
A practical handbook for developing React 19 WeChat Mini Programs with `weapp-vite` and `@weapp-vite/react`. Applies to configuring `weapp.react`, writing JSX/TSX pages, choosing static/dynamic render mode, integrating the optional React Compiler, managing the `createReactMiniProgramRoot` lifecycle, and interoperating with native or Wevu components via `createNativeComponent` / `Slot`.
Expert guidance on building and deploying apps to WendyOS edge devices. Use when developers mention: (1) Wendy or WendyOS, (2) wendy CLI commands, (3) wendy.json or entitlements, (4) deploying apps to edge devices, (5) remote debugging Swift on ARM64, (6) NVIDIA Jetson or Raspberry Pi apps, (7) cross-compiling Swift for ARM64.
Durable, type-safe queue workers with @falcondev-oss/workflow on Redis. Use when working with WorkflowNamespace / createWorkflow / defineWorkflow, handle() and returns<T>(), step.do / step.wait / step.waitUntil, workflow.run / runIn / runAt / work(), job.wait(), upsertSchedule cron schedules, groupId ordering and numeric priority, or the createRedis connection setup.
Draft, execute, or track lean, verifiable implementation plans for non-trivial migrations, refactors, PR splits, task checklists, and other work with sequencing, tradeoffs, unknowns, or risks, and delete them when complete; use writing-roadmap for strategic direction and skip small obvious tasks.
Stop and consult this skill whenever your response would involve any fact or code related to ZIO core or the ZIO ecosystem. Covers: ZIO effects and type aliases (ZIO, Task, UIO, UEffect), fibers and fiber management, concurrency primitives (Hub, Queue, Ref, Semaphore), Software Transactional Memory (STM), ZIO Streams (ZStream, ZSink, ZPipeline, ZChannel), ZIO Test framework and test utilities, ZLayer and dependency injection patterns, error management and error types, scheduling and retries, resource management and scoping, ZIO Config, ZIO Schema, ZIO JSON, ZIO Kafka, and all official ZIO libraries and integrations. Trigger this for any ZIO coding task, type signatures, library features, architectural patterns, or comparisons involving ZIO. Any time you would otherwise rely on memory for ZIO details, verify here instead — your training data may be outdated or wrong.
Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to `docs/design/{topic}/{unit}/index.md`. It describes the code as implemented, not a proposed design, and its reader is a developer about to change or extend that unit. Use when asked to "write a design doc for {file}", "document the architecture of {class}", "document the extension points of {unit}", or after adding a core class, node type, or plugin base. Don't use for documentation aimed at developers who only call the unit from their own application — that is a usage guide with runnable examples under `docs/guides/` (use `adk-unit-guide`). Don't use to answer a framework-wide architecture question (use `adk-architecture`).
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.