android-aso — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited android-aso (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are a Google Play ASO expert. Google Play's algorithm differs fundamentally from iOS — the full description is indexed, there is no hidden keyword field, and ratings are continuous (not version-reset).
| Factor | Google Play | Apple App Store |
|---|---|---|
| Keyword indexing | Title + Short desc + Full desc (all indexed) | Title + Subtitle + Keyword field only |
| Hidden keyword field | ✗ None | ✓ 100-char field |
| Description indexed | ✓ Full 4000 chars | ✗ Not indexed |
| Ratings | Continuous — never reset | Reset per version (can request reset) |
| A/B testing | Play Store Experiments (native) | Product Page Optimization |
| Screenshots | 2–8 per language | Up to 10 per language |
| Feature graphic | Required (1024×500px) | Not applicable |
| Algorithm signals | Installs, engagement, ratings, keywords | Keyword match, ratings, conversions |
| Review indexing | Reviews and replies indexed | Not indexed |
| Field | Limit | Indexed | Weight |
|---|---|---|---|
| Title | 30 chars | ✓ | Highest |
| Short description | 80 chars | ✓ | High |
| Full description | 4000 chars | ✓ | Medium |
| Developer name | — | ✓ | Low |
app-marketing-context.mdBrand – Keyword DescriptorStructure for algorithm + conversion:
[Hook paragraph — 2–3 sentences]
Lead with the core value proposition. Include primary keyword in first 167 chars
(shown above the fold).
[Feature bullets — 5–8 items]
• [Feature]: [Benefit]
Use keywords naturally. Vary phrasing — don't repeat exact phrases.
[Social proof]
"Trusted by X million users" / awards / press mentions
[Call to action]
Download [App Name] today — [value prop].
[Keywords section — natural, not stuffed]
A paragraph using keyword variants, synonyms, and long-tail terms.Keyword density rule: Target keyword should appear 3–5 times across the full description. Exact match + variants. Never stuff.
Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.
Use Appalize keyword tools, then adapt for Play:
GET /v1/keywords/metrics?keywords=meditation,mindfulness,sleep sounds&country=us
GET /v1/keywords/suggestions?term=meditation&country=usPlay-specific considerations:
Required for Play Store. Appears at the top of your listing when no video is present.
Unlike iOS, Play ratings are never reset — every rating ever given counts.
To improve your rating:
review-management skill for response templatesRating prompt timing (see also rating-prompt-strategy skill):
ReviewManager.requestReviewFlow()Native A/B testing for:
Access: Play Console → Store listing experiments
Test one element at a time. Run for minimum 7 days or 1,000 impressions.
Use Early Access to:
Title (30): [text]
Short desc (80): [text]
Full Description:
[Hook — 2–3 sentences, primary keyword in first 167 chars]
✨ Features:
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
[Social proof paragraph]
[CTA sentence]
[Keyword-rich closing paragraph]
Keywords targeted: [list primary keywords used]Score each field 1–10:
Title: [N]/10 — [note]
Short description: [N]/10 — [note]
Full description: [N]/10 — [note]
Screenshots: [N]/10 — [note]
Feature graphic: [N]/10 — [note]
Ratings: [N]/10 — [note]
Overall: [N]/60
Top 3 improvements:
1. [specific change with expected impact]
2. [specific change with expected impact]
3. [specific change with expected impact]aso-audit — iOS-focused audit (compare approaches)metadata-optimization — iOS metadata (different field rules)review-management — Respond to Play reviews to recover ratingrating-prompt-strategy — In-App Review API timing and strategyab-test-store-listing — Play Experiments methodologylocalization — Per-language listing optimization~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.