play-policy-insights
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 acros…
Install / Use
npx skills add android/skills --skill play-policy-insightsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of play-policy-insights
play-policy-insights scores 88/100 on our quality scale, 1488th of 2,780 Automation skills we index.
Its SKILL.md is 8.3 KB long, well organised into 9 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 7,514 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so play-policy-insights is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
play-policy-insights compared with similar skills
All 4 of these similar skills score higher than play-policy-insights; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| play-policy-insights (this skill)by android | 88 | 7.5k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install play-policy-insights?
- Run
npx skills add android/skills --skill play-policy-insights. The install tabs above show the steps for each supported agent. - Which AI agents does play-policy-insights work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is play-policy-insights safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is play-policy-insights still maintained?
- The repository was last updated about 2 months ago, so play-policy-insights is actively maintained.
Skill content
View source on GitHubname: play-policy-insights 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. license: Complete terms in LICENSE.txt metadata: author: Google LLC last-updated: '2026-07-13' keywords:
- account deletion
- accessibility api
- all files access
- audio recording
- audit
- compliance
- contacts access
- data disclosure
- data safety
- data safety label
- data transmission
- demo credentials
- exact alarm
- foreground services
- location access
- login credentials
- manifest hygiene
- package visibility
- permissions hygiene
- photo and video access
- photopicker
- play policy
- pre-submission audit
- privacy policy
- prominent disclosure
- restricted permissions
- scoped storage
- sms and call log
- static analysis
- target sdk
- user consent
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, orspawn_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.
-
Idempotency & Timeout Safeguard: If a sub-agent fails or times out, you MUST verify the presence and integrity of its target output file (e.g.,
<temp_dir>/worker_<goal_name>.json) before retrying. If the file exists and contains valid JSON, treat the execution as SUCCESS and proceed. Otherwise, retry up to three times.
-
-
Fail-fast mandate: The automated audit in Phase 1 is the source of truth. If
orchestrator.pyfails, you must stop immediately with an explanation of failure. Do not use manual auditing as a fallback.
The two-phase protocol
Phase 1: Fact gathering and triage
- Initialize and triage:
- Run
python3 <repo_root>/scripts/orchestrator.py init <app_dir>. - This will create the scratch environment, perform static analysis, map the codebase, identify audit goals, and produce prompts for subagents for each audit goal and prompts for designated critic and aggregator subagents.
- You must wait (up to 5 minutes) for the script to finish.
- Run
- Capture environment: Note values of the
temp_dir, andactivated_goalsfrom the JSON output. You will need them in Phase 2. - Evaluate goals: If
activated_goalsis empty, skip to step 3 of Phase 2 (Aggregation). Otherwise, proceed to step 1 of Phase 2 (Detailed analysis).
Phase 2: Goal-oriented audit
Determine your execution capabilities and proceed with either Mode A OR Mode B.
Mode A: Orchestrator WITH Delegation Capabilities (Parallel)
- Detailed analysis: For each goal in
activated_goals(e.g.,permissions_and_apis,data_safety_part_1,data_safety_part_2), delegate to a sub-agent. Concurrency Limit: You must not spawn more than 3 sub-agents simultaneously. Spawn the first batch of up to 3, wait for their completions, and then spawn the next batch. Repeat until all goals are complete. Pass the prompt:"Read your instructions from <temp_dir>/prompt_worker_<goal_name>.md and execute. MANDATORY: You must use your file-writing capabilities to save your final JSON findings directly to the file system at <temp_dir>/worker_<goal_name>.json. You are strictly forbidden from outputting the JSON in your chat response. To minimize context usage, your final response must be exactly 'SUCCESS' and nothing else."Validate: Confirm every<temp_dir>/worker_<goal_name>.jsonexists and contains valid JSON. If a sub-agent fails or times out, but the valid JSON output file is already present on disk, do NOT retry; proceed normally. Only retry the corresponding worker (up to three times) if the file is missing or invalid. - Aggregate Findings: Execute the python aggregation command:
python3 <repo_root>/scripts/orchestrator.py aggregate <temp_dir>. This producesaggregated_findings.jsonand returns a JSON object containingcritic_chunksrepresenting the number of chunks to verify (e.g.,{"temp_dir": "...", "critic_chunks": 2}). - Parallel Critic review: For each chunk index
ifrom 1 tocritic_chunks, delegate to a sub-agent. Concurrency Limit: You must not spawn more than 3 critic sub-agents simultaneously. Batch them in groups of 3 as above. Pass the prompt:"Read your instructions from <temp_dir>/prompt_critic_<i>.md and execute. MANDATORY: You must use your file-writing capabilities to save your final JSON findings directly to the file system at <temp_dir>/critic_output_<i>.json. You are strictly forbidden from outputting the JSON in your chat response. To minimize context usage, your final response must be exactly 'SUCCESS' and nothing else."Validate: Confirm each<temp_dir>/critic_output_<i>.jsonexists and contains valid JSON before proceeding. If it failed or timed out, but the valid JSON file is present, proceed normally. Otherwise, retry that specific critic chunk. - Proceed to Finalization (Step 4 below)
Mode B: Orchestrator WITHOUT Delegation Capabilities (Sequential)
- Detailed Analysis: For each goal in
activated_goals, sequentially:- Read the contents of
<temp_dir>/prompt_worker_<goal_name>.md. - Execute the instructions contained within that file yourself.
- CRITICAL: You MUST format your findings exactly as requested in the
prompt and save them to
<temp_dir>/worker_<goal_name>.json. Do not summarize findings in your thoughts or chat; move to the next task. - Validate: Confirm
<temp_dir>/worker_<goal_name>.jsonexists before moving to the next goal.
- Read the contents of
- Aggregate Findings: Execute the python aggregation command:
python3 <repo_root>/scripts/orchestrator.py --aggregate <temp_dir>. This producesaggregated_findings.jsonand returns a JSON object containingcritic_chunksrepresenting the number of chunks to verify. - Sequential Critic review: For each chunk index
ifrom 1 tocritic_chunks, sequentially:- Read the contents of
<temp_dir>/prompt_critic_<i>.md. - Execute the steps yourself and save your findings to
<temp_dir>/critic_output_<i>.json. - Validate: Confirm
<temp_dir>/critic_output_<i>.jsonexists before moving to the next chunk.
- Read the contents of
- Proceed to Finalization (Step 4 below)
Finalization (Both Modes)
- Present findings: Run
python3 <repo_root>/scripts/generate_report.py <temp_dir>. It will produce<temp_dir>/compliance_report.md. Present this output file to user. - STOP: The audit is complete. Await further instructions.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
