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.
Profile →npx skills add sickn33/agentic-awesome-skills --skill diagnose-android-overheating --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Overview
- When to Use This Skill
- Safety Stop
- Diagnostic Contract
- Workflow
- 1. Capture an Untouched Baseline
- 2. Choose the Evidence Branch
- 3. Reproduce with a Controlled Comparison
- 4. Correlate, Do Not Guess
- 5. Classify the Finding
- 6. Gate Every Intervention
- Output Format
- Examples
- Idle Heat on Mobile Data
adb devices -l adb -s <serial> shell getprop ro.product.manufacturer adb -s <serial> shell getprop ro.product.model adb -s <serial> shell getprop ro.build.version.release adb -s <serial> shell getprop ro.build.version.sdk adb -s <serial> shell uptime adb -s <serial> shell dumpsys battery adb -s <serial> shell dumpsys thermalservice adb -s <serial> shell dumpsys cpuinfo adb -s <serial> shell top -n 1
What does the diagnose-android-overheating skill do?
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.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill diagnose-android-overheating --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.