file-uploads-v2

name	file-uploads-v2
description	File Uploads & Storage workflow skill. Use this skill when the user needs expert handling of file uploads and cloud storage, especially S3-style object storage, presigned URLs, multipart uploads, and upload security controls. Preserve upstream workflow intent, copied support files, and provenance before merging or handing off.
version	0.0.1
category	devops
tags	["file-uploads-v2","file-uploads","uploads","s3","cloudflare-r2","presigned-urls","multipart-uploads","object-storage","upload-security","omni-enhanced"]
complexity	intermediate
risk	safe
tools	["codex-cli","claude-code","cursor","gemini-cli","opencode"]
source	omni-team
author	Omni Skills Team
license	Unknown
date_added	2026-04-16
date_updated	2026-05-10
source_type	omni-curated
maintainer	Omni Skills Team
family_id	file-uploads-v2
family_name	File Uploads & Storage
variant_id	omni
variant_label	Omni Curated
is_default_variant	true
derived_from	skills/file-uploads-v2
upstream_skill	skills/file-uploads-v2
upstream_author	sickn33
upstream_source	community
upstream_pr	271
upstream_head_repo	diegosouzapw/awesome-omni-skills
upstream_head_sha	93ab394af5645f7127d5003ee02c9566ae5353cd
curation_surface	skills_omni
enhanced_origin	omni-skills-private
source_repo	diegosouzapw/awesome-omni-skills
replaces	["file-uploads-v2"]

File Uploads & Storage

Overview

This skill curates the upstream file-uploads workflow into a safer, more operational guide for designing, reviewing, or debugging file upload systems.

It is optimized for S3-style object storage workflows, especially:

• direct client uploads using presigned URLs
• multipart uploads for large files
• server-side validation and post-upload processing
• Amazon S3 and Cloudflare R2 storage policy differences
• controls that reduce upload abuse, accidental exposure, and orphaned storage costs

Preserve upstream intent and provenance when editing, but use this guide as the execution baseline.

When to Use

Use this skill when the task involves one or more of these conditions:

• users upload files to object storage such as S3 or Cloudflare R2
• the system should avoid proxying large files through the application server
• presigned upload or download URLs need to be designed, reviewed, or tightened
• multipart upload behavior, retries, or cleanup needs debugging
• file validation must distinguish extension, declared MIME type, and actual file signature
• the workflow includes post-upload processing such as image optimization, virus scanning, or metadata extraction
• bucket exposure, ACL usage, lifecycle cleanup, or encryption settings need review

Do not use this skill as the primary guide when:

• the problem is only local filesystem upload handling with no object storage
• the task is a full malware-analysis pipeline design beyond upload gatekeeping
• the main issue is CDN caching, media transcoding, or database blob storage architecture

Workflow

1. Define the upload contract before choosing an API shape

   • Identify allowed file classes, maximum size, retention period, and who may read the object.
   • Decide whether uploads are private-by-default or intentionally public.
   • Separate small-file and large-file paths early; do not force all uploads through one code path.

2. Prefer direct-to-object-store uploads for user content

   • Have the application issue a short-lived presigned URL or multipart upload session.
   • Keep the application server responsible for authorization, naming rules, and metadata policy, not for streaming large bodies.
   • Avoid server proxy uploads unless you need inline inspection that cannot happen asynchronously.