From bkit
bkend.ai file storage expert skill. Covers single/multiple/multipart file upload via Presigned URL, file download (CDN vs Presigned), 4 visibility levels (public/private/protected/shared), bucket management, and file metadata. Triggers: file upload, download, presigned, bucket, storage, CDN, image, 파일 업로드, 다운로드, 버킷, 스토리지, 이미지, ファイルアップロード, ダウンロード, バケット, ストレージ, 文件上传, 下载, 存储桶, 存储, carga de archivos, descarga, almacenamiento, cubo, telechargement, televersement, stockage, seau, Datei-Upload, Download, Speicher, Bucket, caricamento file, scaricamento, archiviazione, bucket Do NOT use for: database operations (use bkend-data), authentication (use bkend-auth).
How this skill is triggered — by the user, by Claude, or both
Slash command
/bkit:bkend-storagebkit:bkend-expertThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Method | Use Case | Process |
| Method | Use Case | Process |
|---|---|---|
| Single | Normal files | Presigned URL -> PUT upload -> Register metadata |
| Multiple | Multiple files | Repeat single upload |
| Multipart | Large files | Initialize -> Part URLs -> Complete |
| Level | Access | URL Type |
|---|---|---|
| public | Anyone | CDN URL (no expiry) |
| private | Owner only | Presigned URL (1 hour) |
| protected | Authenticated users | Presigned URL (1 hour) |
| shared | Specified targets | Presigned URL (1 hour) |
| Category | Max Size |
|---|---|
| Images | 10 MB |
| Videos | 100 MB |
| Documents | 20 MB |
images, documents, media, attachments
| Method | Endpoint | Description |
|---|---|---|
| POST | /v1/files/presigned-url | Generate presigned URL |
| POST | /v1/files | Register metadata (complete upload) |
| GET | /v1/files | File list |
| GET | /v1/files/{id} | File detail |
| PATCH | /v1/files/{id} | Update metadata |
| DELETE | /v1/files/{id} | Delete file |
| GET | /v1/files/{id}/download-url | Generate download URL |
| Tool | Purpose |
|---|---|
| 7_code_examples_data | CRUD + file upload code examples |
1. POST /v1/files/presigned-url -> { url, fileId }
2. PUT {url} with file binary + Content-Type header
3. POST /v1/files with { fileId, filename, contentType, size, visibility }
1. POST /v1/files/multipart/init -> { uploadId }
2. POST /v1/files/multipart/urls -> [{ partNumber, url }]
3. PUT each part URL with file chunk
4. POST /v1/files/multipart/complete -> { file }
For the latest storage documentation, use WebFetch:
npx claudepluginhub nddot/bkit-claude-codeCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.