Skills — ExecBro | Guided React Native Debugging Workflows

Available Skills

Skill	Description
session-setup	Bootstrap a debugging session: discover devices, boot simulators, connect to Metro
debug-logs	Capture, filter, and analyze console logs to find errors and warnings
network-inspect	Monitor and inspect HTTP requests, filter by status/method, and analyze failures
app-state	Inspect Redux/Apollo/context state, navigate the app, and execute code in the runtime
component-inspect	Inspect React component tree, props, state, and layout
layout-check	Verify UI layout against design specs using screenshots and component data
device-interact	Automate device interaction: tap, swipe, text input, and element finding
bundle-check	Detect and diagnose Metro bundler errors and compilation failures
native-rebuild	Rebuild and verify the app after installing native Expo packages

Installing Skills

Claude Code loads each skill from its own folder, with the content in SKILL.md: .claude/skills/debug-logs/SKILL.md. A flat file in .claude/skills/ is never loaded. Install each skill into its own folder:

Install all skills

curl -s https://api.github.com/repos/igorzheludkov/execbro/contents/skills \
  | grep download_url \
  | cut -d '"' -f 4 \
  | while read -r url; do
      name=$(basename "$url" .md)
      mkdir -p ".claude/skills/$name"
      curl -sL "$url" -o ".claude/skills/$name/SKILL.md"
    done

Or pick individual skills from the skills/ folder and save each <name>.md as .claude/skills/<name>/SKILL.md.

Usage

Invoke skills in Claude Code with slash commands:

/session-setup
/debug-logs
/network-inspect

Skills can also be triggered automatically— each skill file contains a "When to Trigger" section that tells Claude when to proactively invoke it without a slash command. For example, Claude will run bundle-check on its own when it detects a red screen, or session-setup when starting a fresh debugging task with no connection established yet.