extracting-logs-with-logcat

Extract and filter Android device logs using adb logcat.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill extracting-logs-with-logcat-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extracting-logs-with-logcat
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/adb/observability/extracting-logs-with-logcat
Command: npx skills add https://github.com/trancee/MeshLink-template --skill extracting-logs-with-logcat-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of overwhelming and unorganized device logs, allowing developers to isolate specific application behavior, debug crashes, and capture diagnostic data for CI/CD pipelines without saturating system resources.

Core Features & Use Cases

  • Efficient Filtering: Filter logs directly on the device using tag and priority expressions to prevent transport congestion.
  • CI/CD Integration: Automate log capture-on-failure patterns with snapshot dumps and buffer management.
  • Advanced Diagnostics: Utilize structured JSON output, buffer rotation, and PID-specific tracking to diagnose complex issues like Doze-mode kills or system-server crashes.

Quick Start

Use the extracting-logs-with-logcat skill to dump all logs from the main and crash buffers into a file named debug-logs.txt after running your test scenario.

Frequently Asked Questions about extracting-logs-with-logcat

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

FAQPage Schema
How do I filter Android logcat output by tag and priority to debug crashes?

Filter Android logcat output by applying tag and priority expressions directly on the device to isolate specific application behavior and prevent transport congestion from overwhelming logs during debugging.

How can I automate adb logcat capture for CI/CD test failures?

Automate adb logcat capture for CI/CD test failures by configuring capture-on-failure workflows that trigger snapshot dumps and manage buffers to extract diagnostic data without saturating system resources.

Can I get structured JSON output from adb logcat for advanced diagnostics?

Structured JSON output from adb logcat is supported for advanced diagnostics, enabling structured analysis of complex issues like Doze-mode kills or system-server crashes on appropriate Android API levels.

What's the best way to track specific process logs in Android logcat buffers?

Track specific process logs in Android logcat buffers by utilizing PID-specific tracking and buffer selection to isolate targeted diagnostic data from main and crash buffers for rapid debugging.

Do I need specific Android API levels to use logcat JSON formatting and PID tracking?

Specific Android API levels are required to use logcat JSON formatting and PID-based tracking, as these advanced diagnostic features depend on platform support for proper execution via adb connectivity.