Skills
98,067 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Google Gemini API integration for building AI-powered applications. Use when working with Google's Gemini API, Python SDK (google-genai), TypeScript SDK (@google/genai), multimodal inputs (image, video, audio, PDF), thinking/reasoning features, streaming responses, structured outputs with JSON schemas, multi-turn chat, system instructions, image generation (Nano Banana), video generation (Veo), music generation (Lyria), embeddings, document/PDF processing, or any Gemini API integration task. Triggers on mentions of Gemini, Gemini 3, Gemini 2.5, Google AI, Nano Banana, Veo, Lyria, google-genai, or @google/genai SDK usage.
Use when adding authentication to a project scaffolded with genesis — login, sessions, SSO, admin users. Asks for an auth tier (basic/standard/strict), derives the mechanism from requirements, and implements it in place following the project's existing conventions.
Detect host inventory and effective CPU, memory, disk, scheduler, container, and accelerator limits when a user asks for resource-aware planning or before a clearly resource-sensitive local workload. Produces a redacted JSON snapshot and conservative planning helpers without stress tests or assuming visible host hardware is usable.
Manage GitHub via GitHub CLI (gh): repos, issues, pull requests, Actions, releases, secrets/variables, projects, gists, searches, and API access. Auto-activates on: "gh", "github cli", "github issue", "github pr", "pull request", "github actions", "workflow", "run", "github release", "release", "gh api", "github repo", "github secret", "github variable", "ci status", "monitor ci", "check ci", "watch ci", "pr dashboard", "pr overview", "open prs", "my prs", "pr status".
Manage Globalize translation resources using the CLI. Use this skill when the user asks to create a translation project, add or remove languages, connect a GitHub or GitLab repository, manage glossaries or style guides, invite team members, manage API keys, or perform any Globalize platform operation. Also use when the user mentions managing translations, translation workflow, or wants to "set up translations for this repo." This skill assumes the CLI is already installed and authenticated — run globalize-now-account-setup first if not.
GO Feature Flag (GOFF) self-hosted feature flag solution with OpenFeature integration. Covers flag configuration, relay proxy, targeting rules, rollouts. Use when user mentions GO Feature Flag, GOFF, gofeatureflag, self-hosted feature flags, or flags.goff.yaml configuration.
Designs and troubleshoots responsive Godot 4.x Control interfaces using anchors, containers, themes, focus navigation, keyboard and controller input, localization-safe sizing, and accessibility practices. Use when requests mention menus, HUDs, forms, responsive layouts, Control nodes, themes, focus, UI input, or accessible interaction.
Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is specified. For React use gsap-react.
Generate customized .claude/ harness framework with Fusion Architecture (GAN-inspired + Domain Specialists). TRIGGER when user wants to set up AI-assisted development structure, create a new project harness, add structure to existing projects, or mentions 'harness', 'scaffold', 'framework setup'. Supports all domains through template + dynamic generation.
Thoroughly analyze a single function by first recovering its type definitions, constant definitions, vtables, function name and signature, then producing the final decompilation. Use when the user wants a complete per-function analysis following the strict recovery order: types → constants → vtables → function identity → decompilation.
Create and manage Home Assistant YAML configuration files including automations, scripts, templates, blueprints, Lovelace dashboards, and file organization. Use when working with Home Assistant configuration files (.yaml, .yml) or discussing HA automations, scripts, sensors, or dashboards.
Turn a vague idea or feature request into a written, reviewable spec and implementation plan before any code is written. Use when the user says "I want to build X", "help me think through", "I have an idea", or hands over an underspecified request.
Implements a saved plan through to a tested, independently reviewed pull request, handing it to an agent in its own worktree when possible. Use this skill when the user asks to implement, execute, or continue a plan. Do not use for creating a plan (use create-plan) or for changes without a plan.
Reference for the `just` command runner — justfile syntax and GitHub Actions integration. Use when an existing repo already has a `justfile` and tasks must be added, modified, or audited. For new mizchi-owned repos, prefer the `pkfire` skill (`Taskfile.pkl` + `pkf`) instead; justfile is kept only for compatibility with existing repos.
Smart Label Capture (Scandit `LabelCapture`) in React Native projects — extracting multiple fields (price, expiry date, serial or lot number, weight) from a label in one scan, using barcode fields plus text fields with regex patterns. Use for integration, label-definition configuration, captured-label handling, the Validation Flow, and SDK version migration.
Smart Label Capture (Scandit `LabelCapture`) in web/browser (TypeScript/JavaScript) projects — extracting multiple fields (price, expiry date, serial or lot number, weight) from a label in one scan, using barcode fields plus text fields with regex patterns. Use for integration, label-definition configuration, captured-session handling, overlay UI, the Validation Flow, and SDK version migration.
Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps. Use when building or reviewing Laravel apps — controllers, Eloquent, service layers, queues, or API resources.
Light on-demand engineering skill · frontend design: turn a vague "make it look good" into runnable React/Tailwind/shadcn code + design decision notes — with a visual signature element, self-consistent style (consistent design tokens), scenario fit (academic poster/data dashboard/admin back office/mobile/marketing landing each have different information density), anti-"obviously AI" (purple-blue gradients/Inter/16px radii/giant hero/centered stacking/emoji headings), and visual accessibility (WCAG 2.2). When to use: competition entries/project demos/research system interfaces that need a web page or app UI / reworking an existing frontend / choosing a design system, palette or font / building dashboard, admin, landing or mobile UI. Trigger words: frontend / interface / UI / web page / website / design a page / landing page / landing / dashboard / data dashboard / admin back office / admin / component / React / Vue / Tailwind / shadcn / palette / font / design system / design system / make it look good / frontend design / redesign the interface / redesign. Core discipline: never decide the design direction/tech stack/palette/font for the user — these are decision points; give recommendations + reasons + alternatives and stop to ask the user via AskUserQuestion. Zero local design library: look up inspiration/trends/stack versions online (Awwwards / `npm view` / the WCAG site), mark last_checked, mark unknown if not found, never rely on a stale local library. Deliver runnable code, not empty talk; reuse `_shared/visual_qa` to judge contrast (do not reinvent the WCAG math). Not a DAG node (on demand: produces no findings, does not block the main line).
Use this skill when writing any code that uses LogTape for logging in JavaScript or TypeScript. Covers getting loggers, the structured message syntax, configuration, library author rules, context, lazy evaluation, testing, and common mistakes to avoid. Trigger whenever the user is adding logging to a project, debugging log output, or integrating LogTape with a framework.
Map the big picture around a topic or software repository by identifying its boundaries, layers, actors, components, relationships, flows, history, fault lines, and open questions, then explain how the pieces fit together and where to look next. Use when a user asks to understand a whole field, domain, technology, ecosystem, industry, codebase, architecture, unfamiliar repo, or phrases such as "give me the big picture", "map the landscape", "how does this all fit together?", "help me get oriented", or "what am I missing?"
The conductor for non-trivial development work: takes an idea — however rough — all the way to shipped code, picking the right amount of process (a one-line fix vs. a full product spec) and driving it end to end rather than ad hoc. Triggers on mapping a loose idea into open questions, grilling a plan to shared understanding, researching unknowns, writing a PRD, breaking work into issues, technical or domain design, prototyping UI, implementing a feature, test-driven development, code review, independent verification, writing a PR description, debugging to root cause, improving architecture, or resolving merge conflicts. Not for one-off prose or writing tasks.
Analyze the structure of a 1C metadata object from an XML dump — реквизиты, tabular sections, forms, движения, types. Use to study object structures (instead of reading XML-файлы directly) and as a preparatory step when writing queries and code that works with objects
Systematically migrate a Hardhat V2 project to Hardhat V3, covering core changes (ESM, declarative config, hooks system, network connections) and the full plugin ecosystem (hardhat-deploy, hardhat-verify, @openzeppelin/hardhat-upgrades, and others), coverage tools, and test migration. Use when upgrading any production Hardhat V2 repository to V3.
Expertise in MLIR (Multi-Level Intermediate Representation) and CIR (Clang IR) development for domain-specific compilation and high-level optimizations. Use this skill when building ML compilers, domain-specific languages, or working with multi-level compilation pipelines.
CommunityToolkit.Mvvm Messenger pub/sub for decoupled communication between ViewModels (or any objects). Covers WeakReferenceMessenger vs StrongReferenceMessenger, IRecipient<TMessage>, RequestMessage<T> / AsyncRequestMessage<T> / CollectionRequestMessage<T>, ValueChangedMessage<T>, channels (tokens), and the ObservableRecipient activation lifecycle. Use across WPF, WinUI 3, .NET MAUI, Uno, and Avalonia.
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.
