Skills
Открытый реестр Skills для ИИ-агентов — структурированные промпты и рабочие процессы с рекомендуемыми моделями, примерами и совместимыми инструментами.
Некоторые описания переведены автоматически в рамках пилота и пока не проверены редактором.
Skills
44
Категории
9
Совместимые инструменты
6
Участники
1
Показано 1–21 из 44
Plans safe database schema and data migrations with backwards compatibility, staged rollout, validation, rollback, performance safeguards, and application coordination.
Designs durable API evolution plans with compatibility guarantees, deprecation policy, version negotiation, consumer communication, migration tooling, and operational telemetry.
Превращает незнакомый репозиторий в краткое инженерное руководство по архитектуре, соглашениям, локальной настройке, ключевым путям выполнения и безопасным первым изменениям.
Designs and implements secure, ergonomic Model Context Protocol servers with precise tool schemas, transport selection, authentication boundaries, error contracts, and tests.
Designs durable memory for AI agents, including what to retain, how to retrieve it, privacy boundaries, expiration policies, and evaluation criteria for useful recall.
Converts a design specification or screenshot into accessible, responsive production UI while preserving component boundaries, design tokens, semantic structure, and states.
Produces clear, reviewable architecture decision records that capture context, alternatives, trade-offs, consequences, rollout steps, and reversal criteria.
Designs reliable JSON and typed outputs for LLM features, including schemas, validation, recovery paths, versioning, examples, and contracts for downstream consumers.
Designs caching strategies across the stack to cut latency and load. Chooses cache layers (browser, CDN, application, database), picks patterns (cache-aside, read-through, write-through, write-behind), sets TTLs and eviction policies, and plans invalidation to avoid staleness and stampedes. Produces a layered plan with keys, TTLs, and invalidation rules.
Designs and implements rate limiting for APIs and services. Recommends an algorithm (token bucket, leaky bucket, fixed or sliding window) for the use case, defines per-key and per-endpoint limits, plans distributed enforcement with Redis, and specifies response headers and 429 handling with retry-after. Produces a design plus reference implementation.
Sets up and maintains Git hooks for a repository. Recommends a manager (Husky, Lefthook, or pre-commit), wires up pre-commit and commit-msg hooks for linting, formatting, type checks, secret scanning, and conventional-commit validation, and keeps hooks fast with staged-file filtering. Produces config plus a short contributor guide.
Builds cross-browser extensions on Manifest V3 with background service workers, content scripts, popup and options UIs, and message passing. Covers permissions scoping, storage sync, context menus, and store submission requirements for Chrome, Edge, and Firefox. Emphasizes least-privilege permissions and secure content-script isolation.
Designs and scaffolds ergonomic command-line tools with subcommands, flags, config files, shell completions, and helpful error output. Covers argument parsing conventions, exit codes, stdin/stdout piping, colored output, progress indicators, and cross-platform packaging. Produces maintainable CLIs that follow POSIX conventions and feel great to use.
Implements secure OAuth 2.0 and OpenID Connect flows including authorization code with PKCE, client credentials, and device code grants. Generates token exchange logic, refresh handling, state/nonce validation, and secure token storage. Flags common pitfalls like implicit flow usage, missing PKCE, and insecure redirect URI handling.
Designs routing layers that dispatch requests across multiple LLMs based on task type, difficulty, latency, cost, and reliability. Covers classifier-based and heuristic routing, fallbacks and retries across providers, quality scoring, and A/B evaluation of routing policies. Helps teams get frontier quality where it matters and cheap models everywhere else.
Analyzes LLM usage and reduces inference cost without sacrificing quality. Covers prompt compression, context trimming, caching (prompt and semantic), model routing by task difficulty, batching, structured output to cut retries, and token accounting. Produces a concrete plan with estimated savings and quality guardrails.
Advises on how to evolve APIs without breaking clients. Compares versioning strategies (URI, header, media-type), classifies changes as breaking or non-breaking, and produces deprecation timelines, migration guides, and compatibility shims so teams can ship changes safely.
Models complex application logic as explicit finite state machines and statecharts. Identifies states, events, guards, and side effects; prevents impossible states; and generates implementations (e.g., XState-style) with diagrams. Ideal for wizards, checkout flows, connection lifecycles, and any feature where implicit boolean flags cause bugs.
Designs and implements real-time services using WebSockets and Server-Sent Events. Covers connection lifecycle, heartbeats, reconnection with backoff, room/channel fan-out, backpressure, authentication on upgrade, and horizontal scaling with a pub/sub backplane. Produces production patterns for chat, live dashboards, collaborative editing, and streaming updates.
Builds robust webhook producers and consumers. Covers signature verification, idempotency keys, retry with exponential backoff, dead-letter handling, event ordering, and replay endpoints, and generates handler code plus tests so integrations survive duplicates and outages.
Modernizes legacy codebases incrementally and safely. Establishes characterization tests to lock in current behavior, then applies the strangler-fig pattern, dependency updates, and idiomatic refactors in small verifiable steps, producing a migration plan that avoids big-bang rewrites.
Skills и MCP-серверы
в чём разница?Skillsописывают, что делать
Skill объединяет инструкции, пример промпта и рекомендуемые модели, чтобы агент стабильно выполнял задачу. Skills добавляют знания, а не новые подключения.
MCP-серверыописывают, как подключиться
MCP-сервер расширяет возможности агента, подключая его к реальным системам: базам данных, API и файлам. MCP добавляет подключения и действия, а не инструкции к задаче.
Простое правило: выбирайте Skill, когда модели нужно хорошо выполнить задачу, и MCP-сервер, когда ей нужен доступ к инструменту или системе. Их можно сочетать: Skill может использовать инструменты MCP-сервера.
Создали полезный Skill?
Добавьте SKILL.md в открытый реестр, который поддерживает сообщество.