Loading...
Loading...
Found 1,737 Skills
Use this skill to connect to the Chrome DevTools UI for interactive debugging, UI/UX review, Q&A, showing elements/network requests/panels to the user, inspecting the user's current DevTools selection, and addressing or polling for DevTools UI comment threads.
Create, inspect, update, and delete Mermail task triagers and review recent triager runs. Use when a user explicitly wants mailbox automation, task extraction, triager debugging, or a triager-linked agent conversation. Do not use for choosing the default triager, provisioning a third-party inbox, waiting for verification mail, or processing one live email manually.
Integrate the Synthesia Interactive Avatar into a LiveKit Agent end-to-end — detects the user's existing LiveKit setup and attaches the avatar with the three-line pattern, or scaffolds a complete boilerplate voice agent if none exists. Use when: (1) adding a real-time, interactive, conversational, or lip-sync avatar to a LiveKit agent, app, or site, or switching/swapping avatars mid-session, (2) the user mentions the Synthesia avatar plugin, livekit-plugins-synthesia, synthesia.AvatarSession, or the Interactive Avatar, (3) migrating from another avatar provider (HeyGen LiveAvatar, Tavus, Beyond Presence, Hedra) to Synthesia, (4) debugging Synthesia avatar issues — SynthesiaError (type AUTH, UNKNOWN_AVATAR, TIMEOUT, ...), avatar never joins, avatar joins but no lip-sync, (5) building any voice agent where the user wants a human face on it, even if they don't name Synthesia explicitly.
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
ArcGIS Maps SDK for JavaScript (@arcgis/core, @arcgis/*-components, @arcgis/create) skill for frontend application development, and its public documentation. Use when building, designing, configuring, debugging, upgrading, or explaining an app that uses the SDK - including Core API modules, web components/custom elements, widgets, maps, scenes, link charts, layers, graphics, popups, Arcade, geometry operators, queries/SQL, utility network, CIMSymbols, authentication, routing, editing, guides, tutorials, samples, references, release notes, or app templates.
Container and deployment standards for FastAPI and Python API services - multi-stage Dockerfiles, .dockerignore, uvicorn behind a proxy, healthchecks, migrations, secrets, hardening, image scanning, and Compose with Postgres. Use when writing, reviewing or debugging any of these, when containerizing or deploying a Python API, or when a container exits, fails health checks or shows CVEs, even if the user never says "Docker".
Collect a redacted local diagnostic bundle (logs, config, version, state) for an OpsMill expert hand-off. TRIGGER when: Infrahub is broken/failing/erroring, the user asks for help debugging, wants to collect logs/diagnostics, prepares a hand-off for OpsMill support, or reports a crash/timeout/connection issue (upgrade failure, stuck branch, container CrashLoopBackOff, 500s, OOM). DO NOT TRIGGER when: debugging a check, transform, generator, menu, or schema in the repository (use the infrahub-managing-* skills), a bundle has already been collected and the user wants it analyzed (use infrahub-analyzing-diagnostics), filing a public GitHub issue (use infrahub-reporting-issues), running operational queries (use infrahub-analyzing-data), or planning an upgrade that has not run yet (use infrahub-planning-upgrades).
Creates, modifies and debugs Infrahub check definitions — Python validation logic, GraphQL queries, and YAML-driven tests for proposed change pipelines. TRIGGER when: writing validation checks, creating Python checks, building data quality guards for proposed changes, writing or running tests for a check, modifying or extending an existing check, debugging why a check fails, passes when it should not, or flags the wrong nodes. DO NOT TRIGGER when: designing schemas, querying live data, building transforms or generators.
Databricks AI Runtime, the `databricks air` CLI commands for submitting and managing GPU training workloads on Databricks serverless compute. Use for: writing and submitting `databricks air` workload YAML, choosing an accelerator type and Python environment, passing hyperparameters and secrets, configuring retries, checking run status, listing/cancelling runs, streaming a run's logs and watching its progress, debugging failed runs, GPU pools, multi-container workloads, custom Docker image setup, and converting a workload to a Databricks Asset Bundle.
Use when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
Use when defining or debugging Spring Boot 3 database transaction boundaries, rollback, propagation, optimistic-lock retries, or commit-bound events. For duplicate HTTP commands use idempotency-patterns; for reactive transactions use webflux-reactive-patterns.
Manifest builder. Turns shared understanding into a verifiable Manifest with Deliverables, Acceptance Criteria, Global Invariants, and an Initial Approach. Use when planning features, scoping refactors, debugging complex issues, or when the user asks to define, scope, plan, spec out, make a manifest, or break down a task.