Skip to content
Back to skills

Mobile Runtime Check

ASecurity

Verify a changed mobile journey on identified devices or emulators, including permissions, lifecycle, offline behavior, and platform-specific limits.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 13, 2026
developmentjavascriptjavareactgit

Security analysis

A100/100

Scanned October 13, 2026

npx -y skills add sujith011/agentic-pro-skills --skill mobile-runtime-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mobile Runtime Check?

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

Security grade badge for Mobile Runtime Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sujith011-mobile-runtime-check/badge)](https://www.skillsdirectory.com/skills/sujith011-mobile-runtime-check)

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: mobile-runtime-check
description: "Verify a changed mobile journey on identified devices or emulators, including permissions, lifecycle, offline behavior, and platform-specific limits."
---

# Mobile Runtime Check

## Process
1. Identify the changed journey, platforms, SDK/runtime versions, and native dependencies. Record the test device, OS, build variant, and whether it is a physical device or emulator.
2. Build and run targeted unit/static checks. Then exercise the actual interaction on a connected runtime with accessible logs.
3. Test first launch, denied/granted permissions, cancellation, background/foreground, process recreation, and offline/reconnection when relevant. Include duplicate taps and interrupted submissions.
4. Check navigation/deep links and pending state after restart. Offline writes need explicit conflict, ordering, retry, and cancellation semantics.
5. For camera, location, Bluetooth, notifications, or background services, verify the physical/platform conditions that an emulator cannot establish. A JavaScript-only preview may omit native behavior.
6. Report each platform and lifecycle case separately. Preserve privacy when collecting screenshots and logs.

## Example
A location-sharing screen stops sharing when cancelled. Reopen the app after a process restart and verify the cancelled session is not revived by stale storage or delayed worker events.

## Stop conditions
An offline/unauthorized device connection means runtime checks remain unverified. Do not describe a successful build as successful camera, permission, or background execution.

## Evidence
- Device/build/OS identity.
- Journey and lifecycle observations with logs.
- Physical-device gaps and platform-specific failures.

## Reference
Workflow independently written after reviewing [react-native-architecture](https://github.com/sickn33/agentic-awesome-skills/blob/cb30121a2dfd007531bd2fbefb56f68de927da6a/skills/react-native-architecture/SKILL.md).

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.

Comments

Loading comments…

Newsletter

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