Upload Connection
SkillFiles & storageConfigure Upload storage providers and inspect Upload hooks. Use when storage configuration, provider selection, or Upload connection health is the task.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Upload Connection skill
What this skill tells your AI
The instructions your AI receives, as published by rejot-dev/fragno in apps/backoffice/content/static/skills/upload-connection/SKILL.md and read by ahel’s review.
Use this skill for organization-scoped Upload storage configuration and hook behavior.
Upload configuration
Configuration fields:
provider: provider to configure:database,r2-binding, orr2.defaultProvider: default provider to use after configuration.r2: R2 provider credentials/configuration payload. Secret.r2Binding: R2 binding provider configuration payload.
Setup notes:
databaseis the simplest provider when external object storage is not required.- Use
r2-bindingwhen storage is provided by Worker bindings. - Use
r2when explicit R2 credentials/config are needed.
Upload events
Cataloged automation events:
source:upload,eventType:capability.configured— fires after Upload is configured for an organization for the first time.
Upload hook work is available under the upload hook scope.
Upload tools
Prepared file lifecycle operations are documented by the using-prepared-uploads skill.
Use Backoffice connection tools for configuration and status, and hook tools for queued hook inspection.
Signals
- GitHub stars
- 61
- Forks
- 6
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
upload-connection- Source
- github.com/rejot-dev/fragno