agentleFS
Sign inStart free
krutikJainkrutikJain/android-agent-skills/.github/skills/android-media-files-sharing/SKILL.md

android-media-files-sharing

Skill14 starsChanged 8 months agoMITView on GitHub

Use modern Android file, media, picker, FileProvider, and share-sheet APIs with minimal permissions.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the request is about: android file sharing, photo picker android app, fileprovider setup android.

    line 17
  2. Distinctive:

    Start with the asset movement path: pick existing media, open a document, create/export a file, capture new content, or share app-owned …

    line 25
  3. Distinctive:

    Keep file ownership and URI grants explicit with app-private storage, MIME types, temporary grants, and stable authorities.

    line 27
  4. Distinctive:

    Prefer Photo Picker, SAF, and chooser APIs over broad media or storage permissions where possible.

    line 32
  5. Distinctive:

    Keep exported authorities, MIME types, and cache cleanup explicit.

    line 34
  6. Distinctive:

    Treat recipients outside your app as untrusted.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-results only when the hard part is the runtime permission flow itself.
  • Handoff skills when the scope expands:
  • android-permissions-activity-results
  • android-security-best-practices

Workflow

  1. 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.
  2. Choose the narrowest platform surface first: Photo Picker, SAF contracts, FileProvider, or chooser-based sharing before considering broad storage permissions.
  3. Keep file ownership and URI grants explicit with app-private storage, MIME types, temporary grants, and stable authorities.
  4. Validate return flows, absent-capability fallbacks, and recipient-app interoperability instead of testing only the happy path.
  5. 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 of FileProvider URIs.
  • 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free