Приложение Промто · Скиллы
Скилл — это записанный порядок работы: как оформлять посты, каким тоном писать клиентам, что проверять перед публикацией. Один раз объяснили — дальше агент делает так всегда.
СкиллыКаталог
Навык — это готовая инструкция для агента: как делать презентацию, вести рефакторинг, оформлять отчёт. Подключается к задаче в приложении «Скиллы», описания у большинства — авторские, на языке оригинала.
Навык — это папка с инструкцией в markdown: как делать работу, на что смотреть, чего избегать. Свой можно написать прямо в проекте и передать агенту, а чужой — установить по ссылке на репозиторий.
Правила оформления документов, тон писем, порядок ревью — то, что вы каждый раз объясняете заново, записывается навыком один раз и работает во всех задачах проекта.
Показаны 2353–2376 из 5 115
Implement Clay load testing, auto-scaling, and capacity planning strategies. Use when running performance tests, configuring horizontal scaling, or planning capacity for Clay integrations. Trigger with phrases like "clay load test", "clay scale", "clay performance test", "clay capacity", "clay k6", "clay benchmark".
jeremylongshore
Исходник →Execute Clay major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Clay, performing major version upgrades, or re-platforming existing integrations to Clay. Trigger with phrases like "migrate clay", "clay migration", "switch to clay", "clay replatform", "clay upgrade major".
jeremylongshore
Исходник →Set up comprehensive observability for Clay integrations with metrics, traces, and alerts. Use when implementing monitoring for Clay operations, setting up dashboards, or configuring alerting for Clay integration health. Trigger with phrases like "clay monitoring", "clay metrics", "clay observability", "monitor clay", "clay alerts", "clay tracing".
jeremylongshore
Исходник →Implement Clay lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Clay integrations, implementing pre-commit hooks, or configuring CI policy checks for Clay best practices. Trigger with phrases like "clay policy", "clay lint", "clay guardrails", "clay best practices check", "clay eslint".
jeremylongshore
Исходник →Execute Clay production deployment checklist and rollback procedures. Use when deploying Clay integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "clay production", "deploy clay", "clay go-live", "clay launch checklist".
jeremylongshore
Исходник →Implement Clay rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Clay. Trigger with phrases like "clay rate limit", "clay throttling", "clay 429", "clay retry", "clay backoff".
jeremylongshore
Исходник →Implement Clay reference architecture with best-practice project layout. Use when designing new Clay integrations, reviewing project structure, or establishing architecture standards for Clay applications. Trigger with phrases like "clay architecture", "clay best practices", "clay project structure", "how to organize clay", "clay layout".
jeremylongshore
Исходник →Implement Clay reliability patterns including circuit breakers, idempotency, and graceful degradation. Use when building fault-tolerant Clay integrations, implementing retry strategies, or adding resilience to production Clay services. Trigger with phrases like "clay reliability", "clay circuit breaker", "clay idempotent", "clay resilience", "clay fallback", "clay bulkhead".
jeremylongshore
Исходник →Implement Clay webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Clay event notifications securely. Trigger with phrases like "clay webhook", "clay events", "clay webhook signature", "handle clay events", "clay notifications".
jeremylongshore
Исходник →Troubleshoot common Clerk errors and issues. Use when encountering authentication errors, SDK issues, or configuration problems with Clerk. Trigger with phrases like "clerk error", "clerk not working", "clerk authentication failed", "clerk issue", "fix clerk".
jeremylongshore
Исходник →Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".
jeremylongshore
Исходник →Optimize Clerk costs and understand pricing. Use when planning budget, reducing costs, or understanding Clerk pricing model. Trigger with phrases like "clerk cost", "clerk pricing", "reduce clerk cost", "clerk billing", "clerk budget".
jeremylongshore
Исходник →Collect comprehensive debug information for Clerk issues. Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues. Trigger with phrases like "clerk debug", "clerk diagnostics", "clerk support ticket", "clerk troubleshooting".
jeremylongshore
Исходник →Configure Clerk for deployment on various platforms. Use when deploying to Vercel, Netlify, Railway, or other platforms, or when setting up production environment. Trigger with phrases like "deploy clerk", "clerk Vercel", "clerk Netlify", "clerk production deploy", "clerk Railway".
jeremylongshore
Исходник →Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk SAML".
jeremylongshore
Исходник →Create your first authenticated request with Clerk. Use when making initial API calls, testing authentication, or verifying Clerk integration works correctly. Trigger with phrases like "clerk hello world", "first clerk request", "test clerk auth", "verify clerk setup".
jeremylongshore
Исходник →Incident response procedures for Clerk authentication issues. Use when handling auth outages, security incidents, or production authentication problems. Trigger with phrases like "clerk incident", "clerk outage", "clerk down", "auth not working", "clerk emergency".
jeremylongshore
Исходник →Install and configure Clerk SDK/CLI authentication. Use when setting up a new Clerk integration, configuring API keys, or initializing Clerk in your project. Trigger with phrases like "install clerk", "setup clerk", "clerk auth", "configure clerk API key", "add clerk to project".
jeremylongshore
Исходник →Set up local development workflow with Clerk. Use when configuring development environment, testing auth locally, or setting up hot reload with Clerk. Trigger with phrases like "clerk local dev", "clerk development", "test clerk locally", "clerk dev environment".
jeremylongshore
Исходник →Configure Clerk for multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing multiple Clerk instances, or implementing environment promotion. Trigger with phrases like "clerk environments", "clerk staging", "clerk dev prod", "clerk multi-environment".
jeremylongshore
Исходник →Implement monitoring, logging, and observability for Clerk authentication. Use when setting up monitoring, debugging auth issues in production, or implementing audit logging. Trigger with phrases like "clerk monitoring", "clerk logging", "clerk observability", "clerk metrics", "clerk audit log".
jeremylongshore
Исходник →Optimize Clerk authentication performance. Use when improving auth response times, reducing latency, or optimizing Clerk SDK usage. Trigger with phrases like "clerk performance", "clerk optimization", "clerk slow", "clerk latency", "optimize clerk".
jeremylongshore
Исходник →Production readiness checklist for Clerk deployment. Use when preparing to deploy, reviewing production configuration, or auditing Clerk implementation before launch. Trigger with phrases like "clerk production", "clerk deploy checklist", "clerk go-live", "clerk launch ready".
jeremylongshore
Исходник →Understand and manage Clerk rate limits and quotas. Use when hitting rate limits, optimizing API usage, or planning for high-traffic scenarios. Trigger with phrases like "clerk rate limit", "clerk quota", "clerk API limits", "clerk throttling".
jeremylongshore
Исходник →Примеры
Нажмите на сам пример, чтобы открыть результат крупно в интерактивном iframe. Кнопка «Использовать пример» перенесёт референс или готовый промпт в Промто.
Что умеет
Один и тот же порядок работы применяется к каждой задаче, а не объясняется заново.
Тон, оформление и правила подачи закрепляются и соблюдаются автоматически.
Скилл живёт в проекте: им пользуются все, кто в нём работает.
Инструкцию можно дополнить или отключить — это обычный текст, а не чёрный ящик.
Обычными словами: что делать, чего избегать, на что смотреть.
Правило закрепляется за проектом.
Агент применяет скилл сам, без напоминаний.
Сценарии
Единый тон во всех текстах — от постов до писем.
Список того, что нужно сверить, чтобы не выпустить ошибку.
Новый человек в проекте получает те же правила, что и агент.
Вопросы
Сообщение действует один раз, скилл — постоянно. Он применяется к каждой новой задаче в проекте.
Несколько: под тексты, под оформление, под проверки. Полезнее держать их короткими и по одному правилу на скилл.
Да, достаточно сказать об этом в задаче — либо временно выключить скилл в приложении.
Приложение работает в браузере: ничего не нужно устанавливать, VPN не требуется, оплата — российскими картами.
