Borrowing it
Nothing to install: this file belongs to baijum/ukulele-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/baijum/ukulele-companion/main/.cursor/skills/play-store-promote/SKILL.mdgit clone --depth 1 https://github.com/baijum/ukulele-companionWrote 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.
[](https://agentmods.dev/skills/baijum/ukulele-companion/play-store-promote)<a href="https://agentmods.dev/skills/baijum/ukulele-companion/play-store-promote"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/play-store-promote/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.
<a href="https://agentmods.dev/skills/baijum/ukulele-companion/play-store-promote"><img src="https://agentmods.dev/badge/skills/baijum/ukulele-companion/play-store-promote.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 12 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 12 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.00674 |
| Opus 5 | $0.00028 | $0.00337 |
| Sonnet 5 | $0.00011 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
play-store-promote 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Play Store Promote
Promote a release from the internal testing track to one of the closed testing tracks using the Gradle Play Publisher (GPP) plugin.
Prerequisites
- Release already uploaded to internal testing (via play-store-upload or android-release)
- Service account key at
app/play-service-account.json - Service account has "Release to testing tracks" permission in Play Console
Workflow
Step 1: Choose the target track
Ask the user which closed testing track to promote to:
| Track | Name in Play Console |
|---|---|
| Alpha | Alpha |
| App Hive Testing | App Hive Testing |
Step 2: Promote the release
Promote to Alpha:
./gradlew promoteReleaseArtifact --from-track internal --promote-track alpha --release-status completed
Promote to App Hive Testing:
./gradlew promoteReleaseArtifact --from-track internal --promote-track "App Hive Testing" --release-status completed
- Use
block_until_ms: 60000(promotion typically takes 10-30s). - The
--from-track internalflag tells GPP to take the latest release from internal testing. - The
--release-status completedflag makes the release immediately available to testers.
Step 3: Report result
After a successful promotion, provide:
- Confirmation of the source track (internal) and destination track
- Link to Play Console: https://play.google.com/console/developers/apps/com.baijum.ukufretboard/tracks
Quick Reference
| Task | Command |
|---|---|
| Promote to Alpha | ./gradlew promoteReleaseArtifact --from-track internal --promote-track alpha --release-status completed |
| Promote to App Hive Testing | ./gradlew promoteReleaseArtifact --from-track internal --promote-track "App Hive Testing" --release-status completed |
| Promote to production | ./gradlew promoteReleaseArtifact --from-track internal --promote-track production --release-status completed |
| Staged rollout to production | ./gradlew promoteReleaseArtifact --from-track internal --promote-track production --release-status inProgress --user-fraction 0.1 |
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.
- 12d ago First seen · 66 lines · 56 tokens per session scan A 13b9792d1ca7
play-store-promote is a skill published in the GitHub repository baijum/ukulele-companion (14 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 674 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-30.
Other skills, from other repositories
sceneview-ios
Build 3D and AR apps on Apple platforms (iOS, macOS, visionOS) with SceneViewSwift — the SwiftUI wrapper around RealityKit. Use whenever the user asks for "3D in SwiftUI", "AR with ARKit in SwiftUI", a model viewer for iOS, or any Apple-platform 3D/AR app where the dependency is the SceneViewSwift Swift Package from…
sceneview
Build 3D and AR apps with the SceneView SDK in Jetpack Compose, SwiftUI (iOS/macOS/visionOS via SceneViewSwift), Web (Filament.js), Flutter and React Native. Use whenever the user asks for "3D in Compose", "AR with ARCore in Compose", a model viewer, or any cross-platform 3D/AR app where the dependency is…
compose-animations
Use when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one state, switching composable content, or choosing between AnimatedVisibility, animateAsState, rememberTransition, AnimatedContent, and Crossfade.
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
compose-state-and-effects
Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders, LaunchedEffect, DisposableEffect, SideEffect, Flow collection, navigation, snackbar, analytics, or focus requests.
android-benchmark-comparison
Use when comparing physical Android benchmark configurations, investigating inconsistent rankings, or selecting an Android default from measured results. Do not use for code-level Compose performance diagnosis without a configuration comparison.