Automated summary
Stops an Android app on a connected device using adb force-stop for clean termination during development.
Strengths
- Safely terminates all app processes without deleting data
- Can be run repeatedly without errors even if app is not running
- Integrates smoothly into deployment and testing workflows
- Uses Android framework command for clean shutdown rather than OS kill
Limitations
- Requires ADB installed and a device connected with USB debugging
- Only stops one specific app (package name must be known)
- Does not clear app data; separate command needed for that
Use when you need to stop the current app before installing a new version, restarting, or testing from a clean process state.
Do not use if you need to completely reset app data (SharedPreferences, databases) – use 'pm clear' instead.
Security analysis
SafeThe skill uses adb shell force-stop for legitimate Android app termination, with no destructive, exfiltrating, or obfuscated commands. It is standard tool usage for development.
No concerns found
How this analysis is madeExamples
Stop the Android app currently running on the device so I can install a new version.Kill the app without removing its data, using force-stop via adb.Terminate the Android app, then restart it after making some config changes.name: android-stop-app description: Stop the Android app running on connected device. Cleanly terminates the app using force-stop. Use when stopping the app for debugging, testing, or cleanup.
Android Stop App
Overview
Stops the Android app running on a connected device by using adb shell am force-stop. This cleanly terminates all app processes, clearing memory while preserving app data.
When to Use
Invoke this skill when the user:
- Asks to "stop the Android app"
- Wants to "kill the app"
- Says "terminate the Android app on device"
- Mentions shutting down or closing the Android app
- Needs to stop before deploying new version
Prerequisites
- Android device connected via USB
- USB debugging enabled
- ADB installed (
brew install android-platform-tools) - Device authorized
- App must be running on the device
Instructions
-
Navigate to the Android app directory:
cd path/to/android/app -
Run the stop script:
./stop-app.sh -
The script will:
- Use
adb shell am force-stopto terminate the app - Report success
- Use
-
Inform the user:
- The app has been stopped
- Safe to call even if app isn't running
- Uses force-stop for clean shutdown (not kill)
Expected Output
🛑 Stopping NoobTest on device...
✅ App stopped
How It Works
The script uses:
adb shell am force-stop com.miso.noobtest
This Android framework command:
- Stops all processes associated with the package
- Clears app from memory
- Preserves app data and settings
- Clean shutdown (not emergency kill)
force-stop vs kill
force-stop (recommended):
- Android framework command
- Clean shutdown
- Preserves app data
- Safe for development
kill (not recommended):
- OS-level signal
- Abrupt termination
- May leave resources in inconsistent state
- Only use if force-stop fails
Common Use Cases
Before deploying new version:
./stop-app.sh
./install-device.sh
Pairing with restart:
./stop-app.sh
# Make configuration changes
./restart-app.sh
Clean state testing:
./stop-app.sh
# Clear app data manually if needed
adb shell pm clear com.miso.noobtest
# Then install fresh
Common Issues
"no devices found":
- Check USB connection
- Ensure USB debugging enabled
- Verify authorized:
adb devices - Try:
adb kill-server && adb start-server
"adb: command not found":
- Install Android platform tools:
brew install android-platform-tools - Check PATH includes adb
App still running after force-stop:
- Rare, but check with:
adb shell pidof com.miso.noobtest - If still running, restart device
- Or use:
adb shell pm clear com.miso.noobtest(nukes app data too)
Safety
This script is safe to call repeatedly:
- Won't error if app isn't running
- Uses clean shutdown method
- Reports status clearly
- No risk to app data or installation
Package Name
The script is configured for the specific app's package name (e.g., com.miso.noobtest for Firefly/NoobTest). Package name is defined in build.gradle.kts under applicationId.
Data Preservation
force-stop does NOT clear:
- App installation
- App data (SharedPreferences, databases, files)
- App permissions
- User settings
To fully clear app state, use:
adb shell pm clear com.miso.noobtest
But this will require reinstallation and setup.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/stop-android-app-mm5t8aab/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/stop-android-app-mm5t8aab' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/stop-android-app-mm5t8aab/download' --output '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md.part' && mv '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md.part' '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Prerequisites
- Android device connected via USB
- USB debugging enabled
- ADB installed (
brew install android-platform-tools) - Device authorized
- App must be running on the device
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md' && test -s '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/android-stop-app' && cp -R '.skill-downloads/stop-android-app-mm5t8aab' '.claude/skills/android-stop-app'Cursor
test -f '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md' && test -s '.skill-downloads/stop-android-app-mm5t8aab/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/android-stop-app' && cp -R '.skill-downloads/stop-android-app-mm5t8aab' '.cursor/skills/android-stop-app'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/stop-android-app-mm5t8aab'openskills read 'stop-android-app-mm5t8aab'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/stop-android-app-mm5t8aab/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.