ios-watch-logs

Stream [APP]-prefixed logs from a USB-connected iPhone to console and device-logs.txt.

1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/asnar00/miso --skill ios-watch-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-watch-logs
Source: https://github.com/asnar00/miso/tree/main/.claude/skills/ios-watch-logs
Command: npx skills add https://github.com/asnar00/miso --skill ios-watch-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pymobiledevice3, and includes scripts (resource) components.

What problem does it solve?

This Skill provides real-time, filtered log streaming from a connected iPhone, displaying only relevant app messages. It eliminates the noise of system logs, making debugging iOS applications significantly faster and more focused, and writes logs to a file for later analysis.

Core Features & Use Cases

  • Filtered Log Stream: Focuses on app-specific logs (those with [APP] prefix), cutting through thousands of irrelevant system messages.
  • Real-time Monitoring: Displays logs in the console as they happen and saves them to device-logs.txt for persistent record-keeping.
  • Use Case: When debugging an intermittent crash in your iOS app, use this skill to stream logs and pinpoint the exact sequence of events leading to the failure, without sifting through verbose system output.

Quick Start

Start watching real-time logs from the iOS app on my connected iPhone.

Frequently Asked Questions about ios-watch-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stream real-time logs from my connected iPhone during development?

Real-time log streaming captures live app output from your iPhone to the console and device-logs.txt file. Connect your device via USB, ensure it's trusted, run the watch-logs.py script, and filtered logs prefixed with [APP] appear instantly as your app executes, eliminating system noise.

Can I debug iOS app crashes by filtering logs instead of reading all system messages?

Yes, filtering isolates app-specific logs marked with [APP] prefix, cutting through thousands of irrelevant system messages. This focused view lets you trace the exact sequence of events leading to a crash without sifting through verbose output.

What do I need to set up before monitoring iOS app logs on a USB-connected device?

Prerequisites include pymobiledevice3 installed, a USB-connected iPhone marked as trusted in iOS settings, the target app running on the device, and access to execute watch-logs.py from your development environment.

Does this work with any iPhone app or only specific ones?

It works with any app running on your connected iPhone that outputs logs. The skill captures and filters messages prefixed with [APP], so apps must emit logs in that format to appear in the stream.

Why save logs to a file in addition to displaying them in the console?

File persistence via device-logs.txt preserves log history for later analysis, correlation with crash reports, or sharing with team members—essential for reproducing intermittent issues or post-incident reviews after the console session ends.

Can I use this skill with iOS apps that don't output structured logs?

The skill requires app logs prefixed with [APP] to filter and display them. Apps without this prefix won't appear in the filtered stream, so you'd need to modify app logging or use system-level tools that don't filter by prefix.