3.4K skills · sorted by relevance
Create Convex queries, mutations, and actions with proper validation, authentication, and error handling. Use when implementing new API endpoints.
The English summary is being prepared. Showing the original description.
Revisa cambios de performance de queries ClickHouse y Postgres (vambe-datascience, CRM, réplicas) contra los errores y aprendizajes de la ronda
The English summary is being prepared. Showing the original description.
Find root cause of errors, crashes, regressions, failing tests before any fix. Not for code review or new features.
The English summary is being prepared. Showing the original description.
Genera tickets profesionales de soporte para Meta Business Suite / WhatsApp Business API optimizados para recibir prioridad URGENTE 24hr resolution. Úsala SIEMPRE que el usuario mencione crear un ticket a Meta, escalar un caso WABA, apelar un ban o restricción, reportar un false positive, abrir caso de soporte WhatsApp Business, problema de onboarding, rechazo de template, errores de Cloud API, OTP delivery, verification stuck, BM restricted, display name rejection, o cualquier issue de una WhatsApp Business Account. También activa cuando el usuario dice frases como "ayúdame a redactar un caso para Meta", "necesito reportar esto a soporte", "hay que escalar esto a WhatsApp", "ticket para Meta", o describe un problema de una cuenta de cliente de Vambe sin pedir ticket explícitamente pero claramente necesita uno. También activa ante preguntas del tipo "¿cómo apelar esto?" o "¿qué hago si Meta dice X?" relacionadas con WABA, BM o verificación.
The English summary is being prepared. Showing the original description.
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
The English summary is being prepared. Showing the original description.
Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.
The English summary is being prepared. Showing the original description.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
The English summary is being prepared. Showing the original description.
Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.
The English summary is being prepared. Showing the original description.
Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.
The English summary is being prepared. Showing the original description.
Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.
The English summary is being prepared. Showing the original description.
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
The English summary is being prepared. Showing the original description.
Convert AmeriFlux ERA5 half-hourly meteorological CSV files into EcoSIM hourly climate forcing NetCDF files, compare generated forcing against overlapping measured tower meteorology when a FULLSET file is available, and report large biases or errors. Use when preparing or validating EcoSIM climate inputs for AmeriFlux sites, checking ERA5 against in situ records, diagnosing forcing discrepancies, or writing climate-quality reports. For non-AmeriFlux paper sites that need a fresh Copernicus CDS ERA5 point download by longitude/latitude, use era5-cds-point-download first.
The English summary is being prepared. Showing the original description.
Access the Firebase Emulator Suite (Firestore, Auth, Functions, Hub) via REST and Admin SDK without trial-and-error. Use this skill whenever you read/write/query/clear Firestore Emulator data, create test users or obtain ID tokens from the Auth Emulator, verify Functions triggers, seed/export emulator data, or hit unexpected 403/404 from an emulator endpoint. Consult it BEFORE curling any emulator port — it encodes the auth header and host-resolution rules that otherwise cause retries.
The English summary is being prepared. Showing the original description.
Premium pre-launch waitlist page template — dark charcoal canvas with subtle vignette, drifting portrait video-thumbnail cards, fade-up cascades, glass nav, live-updating join counter, single email form with success/error states. Built for creative-tool / AI / niche-SaaS invite-only launches with hushed exclusive tone, not loud growth-marketing.
The English summary is being prepared. Showing the original description.
Manages Cargo.lock file updates and resolves --locked flag issues in CI/CD. Triggers when user mentions: - "cargo test --locked failed" - "cannot update the lock file" - "Cargo.lock is out of date" - "PR failed with --locked error" - "fix Cargo.lock"
The English summary is being prepared. Showing the original description.
Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
The English summary is being prepared. Showing the original description.
Design traceable functional test conditions across positive, negative, boundary, and error behavior with observable expectations.
The English summary is being prepared. Showing the original description.
Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).
The English summary is being prepared. Showing the original description.
Confiabilidade da plataforma — SLO, error budget, capacidade, resiliência, ponto único de falha e revisão de prontidão. Use quando o usuário disser "SLA", "SLO", "disponibilidade", "resiliência", "aguenta?", "single point of failure", "production readiness", "quanto de folga temos".
The English summary is being prepared. Showing the original description.
Super-skill for developing Haskell projects with cabal nix-style builds. Orchestrates HLS diagnostics, Haddock, Hoogle, source formatting, and cabal-gild into one workflow. Use when writing, editing, refactoring, building, typechecking, fixing compiler errors, renaming symbols, looking up APIs, or changing dependencies in Haskell projects. Treat cabal.project as the source of truth, prefer HLS before full builds, and prefer local docs over remote lookup.
The English summary is being prepared. Showing the original description.
Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.
The English summary is being prepared. Showing the original description.
Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.
The English summary is being prepared. Showing the original description.
Implement comprehensive monitoring, logging, metrics, tracing, and alerting for production applications to ensure reliability and quick incident response. Use when setting up application monitoring, implementing structured logging, creating metrics and dashboards, setting up alerts, implementing distributed tracing, monitoring performance, tracking errors, or building observability into applications.
The English summary is being prepared. Showing the original description.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
The English summary is being prepared. Showing the original description.