How to use the Android Parked Apps for Cars agent skill

What the skill makes the agent do

Parked apps run on Android Auto and Android Automotive OS only while the vehicle is parked. The skill covers three categories: video, games and browsers. When the skill is active, the agent works through the steps in its SKILL.md file and applies them to your existing project.

The agent helps configure AndroidManifest.xml, including the app category, car launcher and automotive feature declarations, hardware requirements, and configuration changes for display moves. It points to Google's car app quality guidelines so you can audit the app against them. It also covers driver-distraction lifecycle handling, media session playback restrictions, and browser sensitive data protection.

• Sets the correct appCategory and intent filters for video, game or browser apps.
• Declares unsupported hardware features with android:required="false" where the source calls for it.
• Checks that configChanges handle moving to or from a distant display.
• Reviews back navigation, orientation and driver-distraction behaviour against the quality guidelines.

Install the skill from the ZIP or the Claude apps

Download the ZIP for this skill from this page and unzip it. For a personal setup, place the unzipped folder in ~/.claude/skills/. To limit it to one project, place it in the project's .claude/skills/ folder instead.

If you use the Claude apps, you can upload the skill under Settings → Capabilities → Skills instead of copying files by hand.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills

Trigger the skill with natural requests

You do not need a special command. Describe the job in plain language and mention the kind of app and the target platform. The skill's description names migrating, building and auditing parked apps, so requests using those words are the clearest triggers.

Your project should contain an Android codebase with AndroidManifest.xml and Gradle build files. The agent searches for these files first, so point it at the right repository.

• "Migrate my video streaming app to run as a parked app on Android Auto."
• "Audit my browser app against the car app quality guidelines before I submit to Google Play."
• "Update the manifest of my game so it declares the parked game category and handles display moves."

Example workflow on a real project

Start with a clear goal such as auditing an existing app. The agent locates the manifest and build files, finds video players, MediaSession classes, orientation calls and WindowInsets handlers, and then reports what it finds against the checklist. The source says the agent should ask permission before adding dependencies unless you tell it otherwise, so expect that question.

Review each proposed manifest change before accepting it. Then test the app against the applicable criteria in Google's car app quality guidelines before submitting it to Google Play for review.

What the skill needs and what it does not do

The skill requires an existing Android project with AndroidManifest.xml and Gradle build files. For the car app quality guidelines, the context is Google Play distribution. The skill does not run scripts and does not use the network, according to its listing.

It is not the right tool for every car app. It does not cover media or audio apps such as music, radio or audiobooks. It also excludes templated Car App Library navigation, point-of-interest, weather, IoT and communication apps designed for use while driving.

• Runs scripts: no
• Uses network: no
• Out of scope: media and audio apps, templated navigation, POI, weather, IoT, communication apps

Safety notes and tips

Because the skill edits manifests and app code, keep your project under version control so you can review and revert changes. Check every change yourself; the skill is a checklist, not a guarantee of acceptance on Google Play.

Note that some features are limited by status. The Browsers category is in beta on Android Automotive OS and unsupported on Android Auto. Beta categories are permitted on internal or closed testing tracks, while open testing and production tracks need acceptance into an early access program.

• Commit your project to version control before the agent edits anything.
• Do not add compatibility mode for apps that support only Android Auto.
• Do not add distractionOptimized metadata set to true on parked activities.
• Check the category status for your target platform before planning a release track.