Configurar y conectar a un emulador de Android utilizando las herramientas argent MCP. Útil al iniciar una nueva sesión en Android, arrancar un emulador, obtener un número de serie del dispositivo o antes de cualquier tarea de interacción con la interfaz de usuario.
Esta habilidad, basada en software-mansion/argent, permite configurar y conectar un emulador de Android mediante las herramientas MCP (Model Context Protocol). Su propósito principal es agilizar el flujo de trabajo de desarrollo móvil, eliminando la necesidad de configuraciones manuales repetitivas. Al integrarse con sistemas como Claude Code, Cursor o Codex, automatiza tareas como el arranque del emulador, la obtención del serial del dispositivo y la preparación del entorno para pruebas de interfaz de usuario. Esto es especialmente útil al iniciar una nueva sesión de desarrollo en Android, garantizando que el emulador esté listo y conectado antes de cualquier interacción. La habilidad se basa en el SKILL.md de software-mansion/argent-android-emulator-setup, y ofrece comandos predefinidos para emular la experiencia de un agente especializado en Android.
npx skills add https://github.com/software-mansion/argent/tree/main/skills/argent-android-emulator-setupConfigurar y conectar a un emulador de Android utilizando las herramientas argent MCP. Usar al iniciar una nueva sesión en Android, arrancar un emulador, obtener un número de serie del dispositivo, o antes de cualquier tarea de interacción con la interfaz de usuario.
This repo contains 9 individual skills — each has its own dedicated page.
Record a reusable flow (scripted sequence of MCP tool calls) that can be replayed later with a single command. Use when the user asks to create, record, or build a flow, or to script a sequence of device actions.
Interact with an iOS simulator, Android emulator, or Electron app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, or checking visible app state after interactions.
Set up and connect to an iOS simulator using argent MCP tools. Use when starting a new session, booting an iOS simulator, getting an iOS UDID, or before any iOS simulator interaction task.
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP) through the same surface. Use when connecting to the runtime, inspecting React components, reading console logs, or evaluating JavaScript.
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.
Step-by-step workflows for developing or debugging React Native apps on iOS simulator or Android emulator. Use when starting the app, debugging Metro, fixing builds, diagnosing runtime errors, or running tests.
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
Profile a React Native Hermes app to measure re-render and CPU performance using argent profiler tools. Use when optimizing for performance, measuring before/after a fix, spotting slow components, diagnosing re-renders, checking CPU hotspots, or producing a ranked issue report.
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".