google-play-setup

google-play-setup is a skill for Claude Code, Codex from Ampli-Group/agentic-mobile-blueprint. It costs 56 tokens per session (1,785 once invoked), scanned A, original, MIT.

A guide for publishing an Android app through Google Play Console, Google's service for managing Play Store apps. It covers the app listing, Android build credentials, and automated submissions through EAS.

In plain words
What is it for?
It is for configuring the Android package name, creating the Play Store listing, completing app requirements, setting up credentials, and preparing CI/CD uploads.
Why use it?
It collects the required setup steps and policy declarations needed before an Android build can be uploaded.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit It is for configuring the Android package name, creating the Play Store listing, completing app requirements, setting up credentials, and preparing CI/CD uploads.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ampli-group/agentic-mobile-blueprint/google-play-setup
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Ampli-Group/agentic-mobile-blueprint --skill google-play-setup
Clone the repo
git clone --depth 1 https://github.com/Ampli-Group/agentic-mobile-blueprint

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for google-play-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/ampli-group/agentic-mobile-blueprint/google-play-setup/github.svg)](https://agentmods.dev/skills/ampli-group/agentic-mobile-blueprint/google-play-setup)
Your own site
<a href="https://agentmods.dev/skills/ampli-group/agentic-mobile-blueprint/google-play-setup"><img src="https://agentmods.dev/badge/skills/ampli-group/agentic-mobile-blueprint/google-play-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for google-play-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/ampli-group/agentic-mobile-blueprint/google-play-setup"><img src="https://agentmods.dev/badge/skills/ampli-group/agentic-mobile-blueprint/google-play-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,785 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.01785
Opus 5 $0.00028 $0.00892
Sonnet 5 $0.00011 $0.00357
Haiku 4.5 $0.00006 $0.00178

Measured 9d ago against content hash 2ff26da18edb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

google-play-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/google-play-setup/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Google Play Setup

Prerequisites

  • Google Play Console account ($25 one-time fee) at play.google.com/console
  • EAS CLI: npm install -g eas-cli && eas login

Required reading — Expo official guides:


Step 1: Configure Android Package Name

Set the package name in app.json before the first build — it cannot be changed after the app is published:

{
  "expo": {
    "android": {
      "package": "com.yourorg.appname"
    }
  }
}

Use reverse domain notation. Must be globally unique on Play Store.


Step 2: Create Play Console App Listing

  1. Go to play.google.com/consoleCreate app
  2. Fill in:
    • App name: Display name
    • Default language: English
    • App or game: App
    • Free or paid: your choice
  3. Accept policies → Create app

Note the Application ID from the URL: play.google.com/console/u/0/developers/.../app/XXXXXXXXXXXXXXXXXX/


Step 3: Complete App Setup Requirements

Google requires these before you can upload any build:

App content declarations (Play Console → Policy → App content):

  • Privacy Policy URL
  • Ads declaration
  • Content rating questionnaire (takes ~2 min)
  • Target audience
  • Data safety form (what data you collect — be honest)

Store listing (Play Console → Grow → Store presence → Main store listing):

  • Short description (80 chars)
  • Full description (4000 chars)
  • Screenshots: Phone (minimum 2), Tablet optional
  • Feature graphic: 1024×500 PNG
  • App icon: 512×512 PNG

None of this blocks the first upload but it does block publishing to users.

"Finish setting up your app" banner — Play Console shows this dashboard banner after app creation. It lists required items before you can publish. Work through them in order — all must be green before the app goes live. This is separate from the store listing itself.

Read the full file on GitHub · 212 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 212 lines · 56 tokens per session scan A 2ff26da18edb

Subscribe to this mod's changes

google-play-setup is a skill published in the GitHub repository Ampli-Group/agentic-mobile-blueprint (4 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,785 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

rn-app-builder

A build workflow for React Native mobile apps, including Expo setup, shared code in a monorepo, login routing, APIs, themes, and releases. A monorepo stores multiple related packages in one code repository.

LSTM-Kirigaya/jinhui-skills · 53 tokens

native-ui

Building native mobile UIs with Expo Router and React Native. Covers routing, navigation, styling, native controls, animations, and platform conventions following Apple Human Interface Guidelines.

wpank/ai · 36 tokens

expo-native-ui

Build beautiful native iOS/Android apps with Expo Router. Covers route structure, native tabs, animations, blur effects, liquid glass, SF Symbols, and platform patterns.

wpank/ai · 38 tokens

writing-react-native-storybook-stories

Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for…

storybookjs/react-native · 83 tokens

setup-react-native-storybook

Set up Storybook for React Native in Expo, React Native CLI, or Re.Pack projects. Use when adding Storybook to a project, configuring metro.config.js with withStorybook, creating .rnstorybook configuration files, setting up Storybook routes in Expo Router, configuring getStorybookUI, or adding the StorybookPlugin to a…

storybookjs/react-native · 102 tokens

uniwind

Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…

uni-stack/uniwind · 130 tokens