Skills
Открытый реестр Skills для ИИ-агентов — структурированные промпты и рабочие процессы с рекомендуемыми моделями, примерами и совместимыми инструментами.
Некоторые описания переведены автоматически в рамках пилота и пока не проверены редактором.
Skills
23
Категории
9
Совместимые инструменты
6
Участники
1
Показано 1–21 из 23
Designs reliable JSON and typed outputs for LLM features, including schemas, validation, recovery paths, versioning, examples, and contracts for downstream consumers.
Превращает незнакомый репозиторий в краткое инженерное руководство по архитектуре, соглашениям, локальной настройке, ключевым путям выполнения и безопасным первым изменениям.
Produces clear, reviewable architecture decision records that capture context, alternatives, trade-offs, consequences, rollout steps, and reversal criteria.
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 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.
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.
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.
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.
Plans and executes safe dependency upgrades across a project. Analyzes current versions, reads changelogs and release notes for breaking changes, sequences upgrades to minimize risk, applies required code migrations, and verifies with builds and tests. Works across npm, pip, Maven, Cargo, and Go modules.
Writes safe, reversible database schema migrations and the corresponding rollback scripts. Plans zero-downtime changes using expand-and-contract patterns, handles data backfills and index creation without locking, and generates migrations for tools like Alembic, Flyway, Prisma, Knex, and Rails ActiveRecord with clear up/down steps.
Designs GraphQL schemas from domain descriptions or existing data models. Produces typed SDL with queries, mutations, subscriptions, input types, enums, and interfaces, following naming conventions, pagination patterns (Relay-style connections), and error-handling best practices. Can also generate resolvers scaffolding and map schemas to existing REST or SQL backends.
Generates mobile application prototypes and implementations for iOS and Android. Creates SwiftUI views, Jetpack Compose layouts, and React Native components from descriptions or wireframe images. Handles navigation patterns, state management, and platform-specific design guidelines.
Interacts with GitHub via the gh CLI for managing issues, pull requests, CI runs, releases, and repository settings. Automates common GitHub workflows including PR creation with proper descriptions, issue triage, release drafting, and CI debugging.
Generates type-safe API client SDKs from OpenAPI specs, API documentation, or example requests. Produces clean, well-typed client code with error handling, retry logic, pagination helpers, and authentication setup. Supports TypeScript, Python, Go, and Rust.
Analyzes and resolves git merge conflicts by understanding the intent of both sides. Examines the conflict markers, surrounding context, and commit history to produce a correct merged result that preserves both changes without breaking functionality.
Generates complete OpenAPI 3.1 specifications from API descriptions, existing code, or route definitions. Includes request/response schemas, authentication, error responses, examples, and server configurations. Produces valid YAML ready for Swagger UI.
Generates production-ready React components with TypeScript, proper props interfaces, accessibility attributes, responsive design, and test files. Follows modern patterns including Server Components, Suspense boundaries, and composition over inheritance.
Generates TypeScript type definitions from various sources — JSON data, API responses, database schemas, or plain descriptions. Produces strict types with proper generics, utility types, discriminated unions, and JSDoc comments.
Designs and implements comprehensive error handling for APIs. Covers error response formats (RFC 7807 Problem Details), HTTP status code selection, error logging strategies, retry logic, and client-friendly error messages with proper i18n support.
Skills и MCP-серверы
в чём разница?Skillsописывают, что делать
Skill объединяет инструкции, пример промпта и рекомендуемые модели, чтобы агент стабильно выполнял задачу. Skills добавляют знания, а не новые подключения.
MCP-серверыописывают, как подключиться
MCP-сервер расширяет возможности агента, подключая его к реальным системам: базам данных, API и файлам. MCP добавляет подключения и действия, а не инструкции к задаче.
Простое правило: выбирайте Skill, когда модели нужно хорошо выполнить задачу, и MCP-сервер, когда ей нужен доступ к инструменту или системе. Их можно сочетать: Skill может использовать инструменты MCP-сервера.
Создали полезный Skill?
Добавьте SKILL.md в открытый реестр, который поддерживает сообщество.