android-adb
Android device control via raw ADB commands. Use for device/emulator discovery, USB or Wi-Fi connection, app launch/force-stop, tap/swipe/keyevent/text input, screenshots, UI hierarchy dump, and ADB troubleshooting.
What this skill does
# Android ADB Reference for controlling Android devices with raw `adb` commands. ## Execution Constraints - Use `adb -s <serial>` whenever more than one device is connected. - Confirm screen resolution before coordinate actions: `adb -s SERIAL shell wm size`. - Ask for missing required inputs before executing (serial, package/activity, coordinates, APK path). - Surface actionable stderr on failure (authorization, cable/network, tcpip state). - Prefer ADB Keyboard broadcast for CJK and special character input when ADB Keyboard is installed. ## Device And Server ```bash # Start ADB server adb start-server # Stop ADB server adb kill-server # List devices adb devices -l # Target a specific device (use when multiple devices are online) adb -s SERIAL <command> ``` ## Wi-Fi Connection ```bash # Enable tcpip (USB required first) adb -s SERIAL tcpip 5555 # Get device IP adb -s SERIAL shell ip route | grep src # or adb -s SERIAL shell ip addr show wlan0 # Connect over network adb connect <ip>:5555 # Disconnect adb disconnect <ip>:5555 ``` ## Device State ```bash # Screen size adb -s SERIAL shell wm size # Current foreground app (package/activity from mCurrentFocus) adb -s SERIAL shell dumpsys window | grep -E 'mCurrentFocus|mFocusedApp' # Get home launcher package (for back-home detection) adb -s SERIAL shell cmd package resolve-activity --brief -c android.intent.category.HOME # Raw shell command adb -s SERIAL shell <command> ``` ## App Lifecycle ```bash # Verify package installed adb -s SERIAL shell pm list packages | grep <package> # Launch by package (via monkey) adb -s SERIAL shell monkey -p <package> -c android.intent.category.LAUNCHER 1 # Launch by activity adb -s SERIAL shell am start -W -n <package>/<activity> # Launch by URI/scheme adb -s SERIAL shell am start -W -a android.intent.action.VIEW -d "<scheme://path>" # Force-stop adb -s SERIAL shell am force-stop <package> ``` ## Input Actions ```bash # Tap adb -s SERIAL shell input tap X Y # Double tap (two taps with short delay) adb -s SERIAL shell input tap X Y && sleep 0.1 && adb -s SERIAL shell input tap X Y # Long press (swipe to same point with duration) adb -s SERIAL shell input swipe X Y X Y 3000 # Swipe adb -s SERIAL shell input swipe X1 Y1 X2 Y2 [duration_ms] # Key event adb -s SERIAL shell input keyevent KEYCODE_BACK adb -s SERIAL shell input keyevent KEYCODE_HOME adb -s SERIAL shell input keyevent KEYCODE_ENTER # Return to home (press BACK repeatedly, check foreground against home launcher) for i in $(seq 1 20); do adb -s SERIAL shell input keyevent KEYCODE_BACK sleep 0.5 # Check if home reached by comparing current focus to home package CURRENT=$(adb -s SERIAL shell dumpsys window | grep mCurrentFocus) echo "Round $i: $CURRENT" done ``` ## Text Input ```bash # Plain text input (ASCII only, spaces escaped as %s) adb -s SERIAL shell input text "hello%sworld" # Input via ADB Keyboard (supports CJK and special characters) # First ensure ADB Keyboard is active: adb -s SERIAL shell ime set com.android.adbkeyboard/.AdbIME # Then send text (base64 encoded): adb -s SERIAL shell am broadcast -a ADB_INPUT_B64 --es msg "$(echo -n 'your text' | base64)" # Clear text via ADB Keyboard adb -s SERIAL shell am broadcast -a ADB_CLEAR_TEXT ``` ## Screenshot And UI Tree ```bash # Screenshot to local file adb -s SERIAL exec-out screencap -p > screenshot.png # Screenshot to device then pull adb -s SERIAL shell screencap -p /sdcard/screen.png adb -s SERIAL pull /sdcard/screen.png ./screen.png # Dump UI hierarchy XML adb -s SERIAL shell uiautomator dump /sdcard/window_dump.xml adb -s SERIAL pull /sdcard/window_dump.xml ./window_dump.xml ``` ## App Install And Uninstall ```bash # Install APK (replace existing) adb -s SERIAL install -r /path/to/app.apk # Uninstall adb -s SERIAL uninstall <package> ``` ## Common Keycodes | Keycode | Description | |---------|-------------| | `KEYCODE_BACK` | Back button | | `KEYCODE_HOME` | Home button | | `KEYCODE_ENTER` | Enter/confirm | | `KEYCODE_DEL` | Delete/backspace | | `KEYCODE_VOLUME_UP` | Volume up | | `KEYCODE_VOLUME_DOWN` | Volume down | | `KEYCODE_POWER` | Power button | | `KEYCODE_TAB` | Tab key | | `KEYCODE_ESCAPE` | Escape key |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.