zebbern/claude-code-guide / skills/r2-upload
r2-upload
UnverifiedUpload files to Cloudflare R2, AWS S3, or any S3-compatible storage (like MinIO) and generate secure, time-limited presigned download links with configurable expiration, typically set to 5 minutes. Use when the user needs to upload a file to cloud storage and get a shareable link, or mentions R2, S3, presigned URLs, temporary links, or file uploads with expiration.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.9 KB |
| SECURITY.md | markdown | 4.8 KB |
| SKILL.md | skill md | 3.4 KB |
| example-config.yml | config | 1.1 KB |
| package.json | manifest | 1.1 KB |
| pnpm-lock.yaml | manifest | 77.3 KB |
| src/index.ts | script | 11.8 KB |
| src/onboard.ts | script | 7.1 KB |
| tsconfig.json | config | 427 B |
README.md
View on GitHub# R2/S3 Upload Skill
> Upload files to Cloudflare R2, AWS S3, or any S3-compatible storage and generate secure presigned download links with configurable expiration.
## Summary
A TypeScript-based MCP skill that lets you upload files to cloud storage and get shareable links. Perfect for quickly sharing files with temporary access. Features multi-bucket support, interactive onboarding, and 5-minute default expiration for security.
**Quick Example:**
- "Upload this report to R2" → Get a 5-minute download link
- "List files in my bucket" → See what's uploaded
- "Delete old-file.pdf" → Clean up storage
## Quick Setup
### Automated (Recommended)
```bash
cd skills/r2-upload
pnpm install
pnpm run onboard
```
This will:
- Install dependencies
- Guide you through credential setup
- Test your connection
- Create the config file
### Manual Setup
1. Install dependencies:
```bash
pnpm install
```
2. Create config file:
```bash
cp example-config.yml ~/.r2-upload.yml
# Edit ~/.r2-upload.yml with your credentials
```
3. Build:
```bash
pnpm run build
```
## Usage
See `SKILL.md` for detailed documentation and examples.
## Cloudflare R2 Setup
1. Go to [Cloudflare Dashboard](https://dash.cloudflare.com) → R2
2. Create a bucket
3. Go to R2 API Tokens: `https://dash.cloudflare.com/<ACCOUNT_ID>/r2/api-tokens`
4. Create a new API token
- **Important:** Apply to specific bucket (select your bucket)
- Permissions: Object Read & Write
5. Copy the Access Key ID and Secret Access Key
6. Note your Account ID from the R2 dashboard URL
7. Use endpoint: `https://<ACCOUNT_ID>.r2.cloudflarestorage.com`
## Custom Domain (Optional)
To use a custom domain for public URLs:
1. In Cloudflare R2, connect your bucket to a custom domain
2. Add the `public_url` field to your bucket config:
```yaml
public_url: https://files.yourdomain.com
```
This allows you to generate clean public URLs instead of presigned ones.
## Security Considerations
⚠️ **Important Security Notes:**
### API Token Scope
When creating your R2 API token:
- ✅ **Apply to specific bucket only** (not account-wide)
- ✅ **Use minimum permissions:** Object Read & Write only
- ❌ **Avoid:** Admin permissions or account-wide access
### Current Protections
- ✅ Config file secured with 600 permissions (owner-only)
- ✅ Presigned URLs expire (default: 5 minutes)
- ✅ UUID prefixes prevent predictable file paths
- ✅ Credentials isolated in external config
### Known Limitations
- ⚠️ No file size limits (be careful with large files)
- ⚠️ No file type restrictions
- ⚠️ No rate limiting
### Best Practices
1. **Keep expiration short** - Default 5m is recommended
2. **Review uploads periodically** - Use `r2_list` to check your bucket
3. **Don't share presigned URLs publicly** unless intended
4. **Rotate credentials** if you suspect compromise
5. **Use different buckets** for different security levels
**See SECURITY.md for detailed security information and recommendations.**
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |