Menu

Individual skill

android-observable-code

When writing or modifying Android code, improve observability with minimal code changes. Reuse or add key-flow logs and stable UI identifiers so Mobile Easy Use can inspect runtime behavior, diagnose issues, and verify changes.

skills/android-observable-code/SKILL.md

Read pinned source

Source commit 79d8da76964b67c5857cd700ea30bf12538b52d0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
9
Repository last updated
Sep 17, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Android Observable Code

Keep observability changes small and local to the requested work. Reuse existing logs and identifiers; preserve behavior and avoid adding dependencies or observability layers.

## Key-flow logs

- Add logs only at useful flow boundaries: entry, important branches, completion, and failure. For asynchronous work, log the actual outcome, not just task submission.
- Use a stable, exact TAG; put event names and relevant outcome values in the message. `Log.d(TAG, "...")` is a simple option. Existing logging wrappers are suitable when their output reaches Android `liblog` with that TAG, which Mobile Easy Use captures.
- Keep logs sparse and free of sensitive data. Ensure they remain enabled in the build used for inspection.

## UI identifiers

- Give relevant native Views stable resource IDs, such as `R.id.form_submit`. Reuse existing IDs; distinguish repeated elements within their parent scope.
- Mobile Easy Use also supports string View tags through `tag::` paths. Reuse suitable existing tags without overwriting tags used by application logic.