# Play Policy Insights

Automated auditor designed to verify Android applications against Google Play Policy...

- Repository: https://github.com/android/skills (10219 stars)
- Category: Design
- License: Complete terms in LICENSE.txt
- Last updated: 2026-10-29
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add android/skills --skill play-policy-insights -g -a claude-code -y`
Codex: `npx skills add android/skills --skill play-policy-insights -g -a codex -y`
Cursor: `npx skills add android/skills --skill play-policy-insights -g -a cursor -y`
Gemini CLI: `npx skills add android/skills --skill play-policy-insights -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add android/skills`

## Description

Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and APIs Hygiene, User Account and Identity, and Data Safety and Privacy domains.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Play Policy Insights: data safety, login credentials, and restricted permissions

You must audit Android apps for three specific policy domains. You must check
data safety, demo login credentials, and restricted permissions.

## Path Resolution

*   **repo_root**: Absolute path to the directory containing this `SKILL.md`.
*   **app_dir**:: Absolute path to the directory containing app's code.
*   **temp_dir**: Absolute path to the scratch directory at the workspace root.
    It is located at `.scratch/play_policy_insights_<uuid>`. **Containment
    Mandate**: You must confine all file system writes, intermediate artifacts,
    and logs strictly to this directory. This ensures the skill remains portable
    and safe across diverse execution environments, including local harnesses
    and CI/CD pipelines, by avoiding reliance on system-level temporary paths or
    user home directories.

## Critical mandates

-   **Execution Mode Awareness** Before starting Phase 2, evaluate if your
    execution environment provides a tool to spawn or delegate tasks to
    general-purpose sub-agents (e.g., tools often named `invoke_agent`,
    `delegate_task`, or `spawn_worker`, using generic agent profiles like
    'generalist' or 'coding_agent').

-   If **YES**, you MUST use **Mode A (Delegation)**.

-   If **NO**, use **Mode B (Sequential Self-Execution)**. You must read the
    prompt files intended for the subagents, follow their instructions, and
    write the expected output files to disk.

-   **Sub-agents orchestration:**

    -   If you use "Mode A (Delegation)", wait for "SUCCESS" confirmation from
        sub-agents to know when they are done.

The rest: https://github.com/android/skills/blob/HEAD/play/play-policy-insights/SKILL.md