AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Migrate Exoplayer To Media3

skill-sunnat629-android-media-pack-migrate-exoplayer-to-media3 · by sunnat629

Compact skill for migrating legacy ExoPlayer 2.x packages to AndroidX Media3 1.10.1.

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-sunnat629-android-media-pack-migrate-exoplayer-to-media3

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-sunnat629-android-media-pack-migrate-exoplayer-to-media3)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
17d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Migrate Exoplayer To Media3? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Trigger

Use when code imports com.google.android.exoplayer2.* or legacy session/notification APIs.

Rules

  • Start with streaming-media-architecture for ownership, KMP split, preload window, and telemetry.
  • Pin Media3 to 1.10.1 through the version catalog.
  • Keep Media3 APIs in Android source sets; expose KMP-safe state/events upward.
  • Do not mix com.google.android.exoplayer2.* and androidx.media3.* after migration.
  • Replace SimpleExoPlayer with ExoPlayer.
  • Replace legacy session/notification APIs with Media3 session/service.
  • Run dependency tree checks for duplicate classes.

Example

com.google.android.exoplayer2.Player -> androidx.media3.common.Player
com.google.android.exoplayer2.ExoPlayer -> androidx.media3.exoplayer.ExoPlayer

Related

  • media3-background-playback-service
  • media3-compose-ui-material3
  • media3-datasources-networking
  • [references/package-mapping.md](references/package-mapping.md) for the full ExoPlayer 2.x to Media3 package map
  • [references/media3-1.10-api-changes.md](references/media3-1.10-api-changes.md) for API movement relevant to this migration

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.