s3-uploader

Upload images or videos to S3/R2 and return canonical URLs for Airtable attachment fields.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/williamsforeal/Cyclone-SS --skill s3-uploader-williamsforeal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s3-uploader
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/global-skills/_deferred/s3-uploader
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill s3-uploader-williamsforeal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you avoid manually uploading images or videos to S3/R2 and copying resulting links by generating a canonical, attachable URL automatically for downstream systems.

Core Features & Use Cases

  • Upload to S3/R2 with public-read access: Targets an S3-compatible CDN endpoint so media can be referenced directly by URL.
  • Canonical URL generation for attachments: Returns a URL specifically formatted for Airtable attachment fields.
  • Use case: Automate media uploads that originate from workflows (for example, generated images or recorded clips) and immediately store shareable URLs for Airtable records.

Quick Start

Ask the system to use the s3-uploader skill, and confirm it is fully implemented rather than a stub by following the build checklist in _buildlist.md before relying on it.

Frequently Asked Questions about s3-uploader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate uploading media to S3 and return URLs for Airtable attachments?

You can automate uploading media to S3 and return URLs for Airtable attachments by routing generated images or videos through an S3/R2-compatible CDN workflow that outputs canonical, public-read links formatted for attachment fields.

Does R2 work with Airtable attachment fields for storing generated media?

R2 works with Airtable attachment fields by serving uploaded media through public-read URLs, allowing generated content pipelines to deterministically pass shareable links directly into downstream database records.

What is the best way to generate shareable links for Airtable records from automated media uploads?

The best way to generate shareable links for Airtable records is to upload media to an S3/R2-compatible endpoint with a public-read ACL, ensuring the returned canonical URLs are strictly formatted for attachment consumption.

Can I use S3 to upload videos and get canonical URLs for document-to-database flows?

You can use S3 to upload videos and get canonical URLs for document-to-database flows by targeting an S3-compatible CDN endpoint, which returns deterministic links suitable for immediate use in Airtable attachment fields.

Why do my Airtable attachment fields fail to consume media URLs from S3?

Airtable attachment fields fail to consume media URLs from S3 when the CDN lacks public-read ACL behavior or the URL formatting is not strict, preventing downstream systems from deterministically resolving the link.

Do I need a public-read ACL to return canonical URLs from R2 for automation workflows?

You need a public-read ACL to return canonical URLs from R2 for automation workflows, ensuring downstream attachment fields can directly reference and consume the uploaded media by its URL.