Skip to content
Back to skills

App Management

ASecurity

Report app storage, stop an app's background work, clear another app's cache and prove it by measuring, open a screen inside another app including from the background, and hand installs and removals to the system installer, reporting honestly what succeeded.

  • 22 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsrustgoshellsecurity

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add GuruProduction/GURUbyUnusLumen --skill app-management --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of App Management?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for App Management
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/guruproduction-app-management/badge)](https://www.skillsdirectory.com/skills/guruproduction-app-management)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: app-management
description: "Report app storage, stop an app's background work, clear another app's cache and prove it by measuring, open a screen inside another app including from the background, and hand installs and removals to the system installer, reporting honestly what succeeded."
allowed-tools: ["appSizes", "forceStopApp", "killBackgroundApp", "clearAppCache", "startAnyActivity", "reorderTasks", "launchFromBackground", "requestInstallApp", "requestUninstallApp"]
when_to_use: "Use when my human asks about app storage, wants an app stopped, opened, cleared, installed, removed or brought to the front, or wants an app opened while I am not on screen. 'What's eating my storage', 'how big is Spotify', 'stop that app', 'clear that app's cache', 'free up some space', 'open my bank', 'install this APK', 'uninstall that game', 'bring Spotify back up', 'open it in the background'."
---

# App management

I report what the phone will actually tell me about other apps, and I name the privilege that stands in the way when it will not.

## The name of every tool here is deliberate

Two of these were going to be called `installApkSilent` and `uninstallAppSilent`. Those names were lies: a silent install needs `INSTALL_PACKAGES`, which is a system privilege an ordinary install does not hold, and the reachable route shows the system installer and therefore **asks the person**.

So they are `requestInstallApp` and `requestUninstallApp`, and every description says the dialog is the person's to complete. A name that overstates a capability is how a tool comes to be trusted for something it never did.

## Storage

`appSizes` reads the platform's storage statistics when Usage access is held, splitting each app into its own files, its data and its cache. Without that grant it falls back to the size of the installed APK.

Every row carries a `source` field saying which measurement produced it, because those are different numbers and confusing them makes a small app look enormous. I read the source before I quote a figure.

## Stopping an app

`forceStopApp` and `killBackgroundApp` both ask the system to close an app's background work. The platform gives **no confirmation** for that call, and the app may restart immediately.

`killBackgroundApp` looks for the app's process before and after and reports `verifiedStopped`. Where another package's process list is not readable, it reports the outcome as **unverified** rather than guessing. "I asked" and "it stopped" are different facts and only the second is worth reporting as done.

Both refuse to target GURU's own package, because the call would be answered by the process it kills.

## Cache

`clearAppCache` actually clears the cache now, by running the platform's own cache-only clear at shell UID, which needs Shizuku. The old version measured the size, opened a Settings page and reported success over a call that cleared nothing, which was a success flag on an action that never happened.

**The proof is the measurement.** It reads the cache size before, clears, and reads it again. It reports the cache as cleared only when the size actually fell, because the command exiting zero proves it ran and not that anything was removed. The result carries both numbers so the change is visible rather than asserted.

Three outcomes it distinguishes rather than blurring: the size fell, which is a real clear; the size could not be measured, which happens without Usage access and means the clear is unknown rather than done; and the size did not move, which is the command being refused or the app rewriting its cache immediately.

Without Shizuku it names that state, opens the app's own storage screen so the person can press Clear cache themselves, and never claims a clear.

It refuses to target GURU itself, because the clear ends the process answering the call and the result would never be reported.

## Opening a screen

`startAnyActivity` builds an intent from a component, an action or the app's launcher screen, **resolves it first**, and then starts it. Resolving first is what separates three outcomes a person acts on differently:

- the screen does not exist,
- the app does not allow it to be opened,
- it opened.

A `SecurityException` means the app chose not to be opened, and no grant changes that. I say so rather than reporting a permission problem.

`reorderTasks` brings an existing task forward with the reorder flag. Since Android 5 an app sees only its own task in the task list, so I say the launch was issued rather than claiming the screen is now in front.

## Opening something while I am not on screen

`launchFromBackground` is the one that works when GURU is not the visible app. Since Android 10 a background `startActivity` is dropped silently, so an ordinary call would report a launch that never happened. This runs the platform's own `am start` at shell UID, which is not subject to that block.

The component is resolved **before** the shell is consulted, which keeps two failures apart: there is no such screen, and the shell is not available. Those need different fixes, so they get different sentences.

`am start` can report a refusal in its own output while still exiting zero, so the output is inspected as well as the exit code. A launch is reported as issued, never as an app that appeared, because nothing can read back what is on screen.

## Installing and removing

`requestInstallApp` checks the file exists, reports its byte size, reads the package identity from the archive, and then hands it to the system installer. It refuses without `confirm`. It never reports a completed install, because the person has not confirmed yet at that moment.

`requestUninstallApp` refuses without `confirm`, refuses to target GURU, and then verifies afterwards whether the package is genuinely gone. Still present means the dialog is still waiting, which is a true statement rather than a failure.

## The mistakes I do not make

I do not call a storage figure without saying which measurement produced it. I do not report a stopped app I could not verify. I do not claim a silent install or a silent uninstall, because neither is reachable. I do not start an activity I have not resolved.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.