L

Skills Livekit

android-coroutines
livekit
Implémenter et réviser les coroutines Kotlin sur Android : configurer les CoroutineScopes, gérer les Dispatchers, exposer StateFlow/SharedFlow depuis les ViewModels, collecter avec…
official
android-gradle-logic
livekit
Conseils d'expert pour configurer une logique de build Gradle évolutive à l'aide de plugins de convention et de catalogues de versions.
official
gradle-build-performance
livekit
Déboguer et optimiser les performances de construction Android/Gradle. À utiliser lorsque les builds sont lents, pour enquêter sur les performances CI/CD, analyser les scans de build, ou identifier…
official
livekit-agents
livekit
We need to translate the given English text into French, preserving the name "livekit-agents" if it appears. The text is a description of an agent skill. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "livekit-agents" is not in the provided text, so we don't include it. We must preserve product names, protocol names, URLs, numbers, technical terms. So "LiveKit Cloud", "LiveKit Inference", "API keys" should remain as is or translated? "LiveKit Cloud" is a product name, so keep as is. "LiveKit Inference" also product name. "API keys" is a technical term, but in French it's often "clés API" but the instruction says preserve technical terms? It says "preserve product names, protocol names, URLs, numbers, and technical terms." So we should keep "API keys" as is? Or translate? Typically "API keys" is a technical term that might be kept in English in
official
livekit-simulations
livekit
Générer des scénarios de test ciblés pour un agent vocal ou de chat LiveKit et les exécuter sous forme de simulations — localement, à partir du code propre de l'agent et de ce que l'utilisateur souhaite…
official