agentsclimarketplace
Sign in

Mobile camera media

Skill ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-camera-media

Use to plan camera and media capture — permissions, capture/pick flows, image/video handling, and resizing/compression before upload. Requires native support (dev build or CLI).From its SKILL.md

Install
npx -y skills add ahtishamshahzad/agent_dev_flow --skill mobile-camera-media

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 564 tokens by cl100k_base, as published. Nobody here has run it

Mobile Camera Media

Purpose

Plan camera/media: request permissions, capture or pick photos/video, and process (resize/compress) media before use/upload.

When to Use

  • When the app captures or picks photos/video/audio.
  • Not on Expo Go for capabilities needing a dev build.

Inputs

  • Media requirements (capture/pick, photo/video, quality).
  • Runtime + build model; upload target (mobile-file-upload).

Discovery Questions

  • Capture, pick from library, or both? Photo/video/audio?
  • What quality/resolution is needed vs bandwidth/storage?
  • How are permissions requested and handled if denied?

Responsibilities

  • Handle camera/library permissions and denial states.
  • Plan capture/pick flows.
  • Resize/compress media before upload to save bandwidth/memory (mobile-performance).
  • Hand off to upload (mobile-file-upload).

Required Workflow

  1. Confirm media needs + native support.
  2. Request permissions; handle denial.
  3. Plan capture/pick + processing (resize/compress).
  4. Hand off to upload.
  5. Record the media plan.

Decision Rules

  • Capabilities requiring native support need a dev build (Expo) or CLI, not Expo Go.
  • Resize/compress before upload — don't send full-resolution originals needlessly.
  • Request permission contextually; handle denial gracefully.

Rules

  • Respect permission models; handle denial.
  • Process media to protect memory/bandwidth.
  • Coordinate upload with mobile-file-upload.

Anti-Patterns

  • Assuming Expo Go covers all capture.
  • Uploading full-resolution originals.
  • No handling for denied permissions.
  • Leaking large media into memory (mobile-performance).

Validation Checklist

  • Native support confirmed.
  • Permissions + denial handled.
  • Capture/pick flows planned.
  • Resize/compress before upload.
  • Handoff to upload defined.

Definition of Done

A recorded media plan: permission handling, capture/pick flows, resize/compress processing, and a clean handoff to upload — with native support confirmed.

Related Skills

mobile-file-upload, mobile-native-modules, mobile-performance, mobile-builds

Related Knowledge

../../../knowledge/ (media requirements).

Related References

../../../references/mobile/native/ when populated.

Context Loading Guidance

  • Requires: media requirements, runtime/build model, upload target.
  • Does not require: unrelated screens, the full mobile skill set, unrelated references.
  • May load: mobile-file-upload, mobile-performance.
  • Stop when: the media plan is recorded.

Token Efficiency Guidance

Plan capture + processing; delegate transfer to file-upload.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most media documents skills give in 564 tokens

Counted across 157 of the 158 authors here whose files we hold, read 2026-08-07

  • Provide posting time recommendationsin 7 of 157, across 5 files
  • Track metrics over time to identify trendsin 6 of 157, across 2 files
  • Read marketing context file before startingin 6 of 157, across 5 files
  • Choose platforms based on audience presencein 6 of 157, across 4 files
  • Adapt tone for each platformin 6 of 157, across 4 files
  • Ensure data completeness before analysisin 5 of 157, across 1 file
  • Compare metrics within same time periodsin 5 of 157, across 1 file
  • Account for platform-specific benchmarksin 5 of 157, across 1 file
  • Separate organic and paid metricsin 5 of 157, across 1 file
  • Include context when interpreting resultsin 5 of 157, across 1 file
  • Keep tweets under 280 charactersin 5 of 157, across 3 files
  • Download top-K results with an attribution sidecarin 5 of 157, across 2 files

Said here and by no other author read

  • confirm native support for media needs
  • request camera and library permissions
  • handle permission denial states gracefully
  • plan capture or pick media flows
  • resize and compress media before upload
  • coordinate upload with file upload skill

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.