Android Media Files Sharing
CommunitykrutikJain
Use modern Android file, media, picker, FileProvider, and share-sheet APIs with minimal permissions.
Overview
- Repository
- krutikJain/android-agent-skills
- Publisher
- krutikJain
- Stars
- 14
- Forks
- 5
- Bundled files
- 5
- License
- MIT
- Updated
- Mar 25, 2026
Installation
tmp=$(mktemp -d)
git clone --depth 1 https://github.com/krutikJain/android-agent-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/android-media-files-sharing" ~/.claude/skills/android-media-files-sharing
rm -rf "$tmp"tmp=$(mktemp -d)
git clone --depth 1 https://github.com/krutikJain/android-agent-skills.git "$tmp"
mkdir -p ~/.codex/skills
cp -R "$tmp/skills/android-media-files-sharing" ~/.codex/skills/android-media-files-sharing
rm -rf "$tmp"Install the Android Media Files Sharing agent skill from https://github.com/krutikJain/android-agent-skills/tree/main/skills/android-media-files-sharing into this project's skills folder.Instructions
Android Media Files Sharing
When To Use
- Use this skill when the request is about: android file sharing, photo picker android app, fileprovider setup android.
- Primary outcome: Use modern Android file, media, picker, FileProvider, and share-sheet APIs with minimal permissions.
- Reach for this skill when the core problem is content URIs, share-sheet flows, picker choice, or app-to-app file exchange. Use
android-permissions-activity-resultsonly when the hard part is the runtime permission flow itself. - Handoff skills when the scope expands:
android-permissions-activity-resultsandroid-security-best-practices
Workflow
- Start with the asset movement path: pick existing media, open a document, create/export a file, capture new content, or share app-owned content to another app.
- Choose the narrowest platform surface first: Photo Picker, SAF contracts,
FileProvider, or chooser-based sharing before considering broad storage permissions. - Keep file ownership and URI grants explicit with app-private storage, MIME types, temporary grants, and stable authorities.
- Validate return flows, absent-capability fallbacks, and recipient-app interoperability instead of testing only the happy path.
- Hand off runtime permission complexity or deeper hardening only after the URI and sharing contract is correct.
Guardrails
- Prefer Photo Picker, SAF, and chooser APIs over broad media or storage permissions where possible.
- Share content with
content://URIs and temporary grants, never raw file paths. - Keep exported authorities, MIME types, and cache cleanup explicit.
- Treat recipients outside your app as untrusted; validate what leaves the app and what comes back.
Anti-Patterns
- Requesting broad media or storage access when Photo Picker or SAF is enough.
- Sharing
file://paths or world-readable files instead ofFileProviderURIs. - Assuming every recipient app handles every MIME type or URI permission correctly.
- Mixing permission-flow design with file-sharing contract design until both become unclear.
Review Focus
- Picker/SAF/FileProvider/chooser selection.
- MIME type, URI authority, and grant lifecycle correctness.
- Minimal-permission media access.
- Recipient-app interoperability and cleanup of temporary files.
Examples
Happy path
- Scenario: Attach and share a task snapshot using the least-privilege API.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest
Edge case
- Scenario: Handle absent picker support or denied media capabilities in the XML fixture.
- Command:
cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest
Failure recovery
- Scenario: Separate media/file flows from permission-only or networking-only requests.
- Command:
python3 scripts/eval_triggers.py --skill android-media-files-sharing
Done Checklist
- The platform surface is narrower than a broad storage permission where possible.
- URI authorities, MIME types, and temporary grants are explicit.
- Picker and share-sheet fallbacks are covered.
- Permission-only work is handed off instead of conflated with the sharing contract.
Official References
- https://developer.android.com/training/data-storage/shared/photopicker
- https://developer.android.com/training/data-storage/shared/documents-files
- https://developer.android.com/training/secure-file-sharing/setup-sharing
- https://developer.android.com/training/sharing/send
- https://developer.android.com/topic/performance/graphics/picker
Bundled files
FAQ
What does Android Media Files Sharing do?
Use modern Android file, media, picker, FileProvider, and share-sheet APIs with minimal permissions.
Who made Android Media Files Sharing?
krutikJain (a community member) publishes it in the krutikJain/android-agent-skills repository on GitHub.
Is Android Media Files Sharing free?
Yes. Android Media Files Sharing is open source, published by krutikJain under the MIT license.
What comes with Android Media Files Sharing?
Its instructions and 5 files the agent reads only when a task needs them, such as references, examples or scripts.
Which agents can use Android Media Files Sharing?
Any coding agent that reads SKILL.md files, including Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI. The agent loads the skill when a task matches its description.
What are agent skills?
An agent skill is a folder with a SKILL.md file: instructions that teach a coding agent how to do one kind of task, and optionally files it can read while it works. The agent keeps only the skill's name and description in mind and reads the rest when a task calls for it.
How are agent skills different from MCP servers?
An MCP server gives an agent new tools to call, code that runs somewhere and returns results. A skill gives it knowledge: how to approach a task with the tools it already has. Many agents use both.
How can my agent test my Android app?
Robomori lets coding agents create, start and control Android emulators and devices from one command, so they can install your app, take screenshots and check dark mode, font sizes and languages.
Provide technical guidance for Android camera development with CameraX. Use when implementing camera features, handling asynchronous recording lifecycles, wiring low-level hardware interop using CameraX, or integrating ML Kit or Media3 effects.
Implements Google Cast support in Android apps using Jetpack Media3. Handles adding build dependencies, updating manifest, configuring OptionsProvider, and managing CastPlayer or RemoteCastPlayer for playback in both Compose and View-based UIs. Use when adding Cast functionality or migrating from legacy Cast SDK to Media3 Cast.
Media player traps on Media3/ExoPlayer and desktop engines: crossfade, audio focus, fades, loudness, DSP, queues and shuffle, position restore, service lifecycle, group listening. Use when playback state, queue or audio levels go wrong.
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 `io.github.sceneview:sceneview` / `io.github.sceneview:arsceneview` / `SceneViewSwift` / `sceneview-web` / `flutter_sceneview` / `@sceneview-sdk/react-native`. Skip for plain ARCore-SDK / Sceneform / Unity / Unreal / RealityKit-without-SceneViewSwift work.
