Agent skill · data analytics · sickn33
diagnose-android-overheating
Use when diagnosing Android overheating, idle heat, thermal throttling, charging or radio heat, or abnormal battery drain with read-only ADB evidence and approval gates.
Why this skill is useful
Provides specific ADB commands and diagnostic workflows for identifying Android overheating issues that the AI wouldn't reliably generate on its own.
What it needs
Requires adb installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Diagnose Android Overheating Overview Find the most likely source of Android device heat by correlating thermal state, battery conditions, CPU activity, wakeups, radios, sensors, charging, and the user's timeline. Keep diagnosis read-only by default, distinguish evidence from inference, and propose only the smallest reversible intervention after the user approves it. When to Use This Skill Use when an Android phone is hot, warm while idle, thermally throttled, shutting down from heat, or draining its battery unusually fast. Use when heat appears during charging, weak cellular signal, 5G use, navigation, camera use, gaming, media playback, tethering, or background activity. Use when the user wants to identify an offending app, service, wakelock, sensor, modem condition, or charging condition through ADB. Use when a previous Android optimization or debloat attempt may have left settings that changed power or thermal behavior. Use for physical phones and tablets. For profiling the energy use of an app under development, use an app-performance skill instead. Safety Stop Stop software diagnosis when the device shows battery swelling, smoke, hissing, leaking, a sharp chemical odor, repeated thermal shutdowns, or heat severe enough that it cannot be handled safely. Tell the user to disconnect power if this can be done safely, power the device off, keep it away from flammable material, and seek manufacturer or qualified repair support. Do not suggest cooling the device in a refrigerator or freezer, puncturing it, continuing to charge it, or running stress tests. Diagnostic Contract Before collecting data: 1. Confirm the user owns or is authorized to inspect the device. 2. Ask what “hot” means: location on the handset, activity, charging state, network type, onset, duration, and whether the heat also occurs while idle. 3. Record the device model, Android version, recent OS/app changes, charger and cable, ambient conditions, and visible thermal warnings. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/diagnose-android-overheating--07d09a