Box Automation via Rube MCP
Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Box connection via
RUBE_MANAGE_CONNECTIONS with toolkit box
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit box
- If connection is not ACTIVE, follow the returned auth link to complete Box OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Upload and Download Files
When to use: User wants to upload files to Box or download files from it
Tool sequence:
BOX_SEARCH_FOR_CONTENT - Find the target folder if path is unknown [Prerequisite]
BOX_GET_FOLDER_INFORMATION - Verify folder exists and get folder_id [Prerequisite]
BOX_LIST_ITEMS_IN_FOLDER - Browse folder contents and discover file IDs [Optional]
BOX_UPLOAD_FILE - Upload a file to a specific folder [Required for upload]
BOX_DOWNLOAD_FILE - Download a file by file_id [Required for download]
BOX_CREATE_ZIP_DOWNLOAD - Bundle multiple files/folders into a zip [Optional]
Key parameters:
parent_id: Folder ID for upload destination (use "0" for root folder)
file: FileUploadable object with s3key, mimetype, and name for uploads
file_id: Unique file identifier for downloads
version: Optional file version ID for downloading specific versions
fields: Comma-separated list of attributes to return
Pitfalls:
- Uploading to a folder with existing filenames can trigger conflict behavior; decide overwrite vs rename semantics
- Files over 50MB should use chunk upload APIs (not available via standard tools)
- The
attributes part of upload must come before the file part or you get HTTP 400 with metadata_after_file_contents
- File IDs and folder IDs are numeric strings extractable from Box web app URLs (e.g.,
https://*.app.box.com/files/123 gives file_id "123")
2. Search and Browse Content
When to use: User wants to find files, folders, or web links by name, content, or metadata
Tool sequence:
BOX_SEARCH_FOR_CONTENT - Full-text search across files, folders, and web links [Required]
BOX_LIST_ITEMS_IN_FOLDER - Browse contents of a specific folder [Optional]
BOX_GET_FILE_INFORMATION - Get detailed metadata for a specific file [Optional]
BOX_GET_FOLDER_INFORMATION - Get detailed metadata for a specific folder [Optional]
BOX_QUERY_FILES_FOLDERS_BY_METADATA - Search by metadata template values [Optional]
BOX_LIST_RECENTLY_ACCESSED_ITEMS - List recently accessed items [Optional]
Key parameters:
query: Search string supporting operators ("" exact match, AND, OR, NOT - uppercase only)
type: Filter by "file", "folder", or "web_link"
ancestor_folder_ids: Limit search to specific folders (comma-separated IDs)
file_extensions: Filter by file type (comma-separated, no dots)
content_types: Search in "name", "description", "file_content", "comments", "tags"
created_at_range / updated_at_range: Date filters as comma-separated RFC3339 timestamps
limit: Results per page (default 30)
offset: Pagination offset (max 10000)
folder_id: For LIST_ITEMS_IN_FOLDER (use "0" for root)
Pitfalls:
- Queries with offset > 10000 are rejected with HTTP 400
BOX_SEARCH_FOR_CONTENT requires either query or mdfilters parameter
- Misconfigured filters can silently omit expected items; validate with small test queries first
- Boolean operators (
AND, OR, NOT) must be uppercase
BOX_LIST_ITEMS_IN_FOLDER requires pagination via marker or offset/usemarker; partial listings are common
- Standard folders sort items by type first (folders before files before web links)
3. Manage Folders
When to use: User wants to create, update, move, copy, or delete folders
Tool sequence:
BOX_GET_FOLDER_INFORMATION - Verify folder exists and check permissions [Prerequisite]
BOX_CREATE_FOLDER - Create a new folder [Required for create]
BOX_UPDATE_FOLDER - Rename, move, or update folder settings [Required for update]
BOX_COPY_FOLDER - Copy a folder to a new location [Optional]
BOX_DELETE_FOLDER - Move folder to trash [Required for delete]
BOX_PERMANENTLY_REMOVE_FOLDER - Permanently delete a trashed folder [Optional]
Key parameters:
name: Folder name (no /, \, trailing spaces, or ./..)
parent__id: Parent folder ID (use "0" for root)
folder_id: Target folder ID for operations
parent.id: Destination folder ID for moves via BOX_UPDATE_FOLDER
recursive: Set true to delete non-empty folders
shared_link: Object with access, password, permissions for creating shared links on folders
description, tags: Optional metadata fields
Pitfalls:
BOX_DELETE_FOLDER moves to trash by default; use BOX_PERMANENTLY_REMOVE_FOLDER for permanent deletion
- Non-empty folders require
recursive: true for deletion
- Root folder (ID
"0") cannot be copied or deleted
- Folder names cannot contain
/, \, non-printable ASCII, or trailing spaces
- Moving folders requires setting
parent.id via BOX_UPDATE_FOLDER
4. Share Files and Manage Collaborations
When to use: User wants to share files, manage access, or handle collaborations
Tool sequence:
BOX_GET_FILE_INFORMATION - Get file details and current sharing status [Prerequisite]
BOX_LIST_FILE_COLLABORATIONS - List who has access to a file [Required]
BOX_UPDATE_COLLABORATION - Change access level or accept/reject invitations [Required]
BOX_GET_COLLABORATION - Get details of a specific collaboration [Optional]
BOX_UPDATE_FILE - Create shared links, lock files, or update permissions [Optional]
BOX_UPDATE_FOLDER - Create shared links on folders [Optional]
Key parameters:
collaboration_id: Unique collaboration identifier
role: Access level ("editor", "viewer", "co-owner", "owner", "previewer", "uploader", "viewer uploader", "previewer uploader")
status: "accepted", "pending", or "rejected" for collaboration invites
file_id: File to share or manage
lock__access: Set to "lock" to lock a file
permissions__can__download: "company" or "open" for download permissions
Pitfalls:
- Only certain roles can invite collaborators; insufficient permissions cause authorization errors
can_view_path increases load time for the invitee's "All Files" page; limit to 1000 per user
- Collaboration expiration requires enterprise admin settings to be enabled
- Nested parameter names use double underscores (e.g.,
lock__access, parent__id)
5. Box Sign Requests
When to use: User wants to manage document signature requests
Tool sequence:
BOX_LIST_BOX_SIGN_REQUESTS - List all signature requests [Required]
BOX_GET_BOX_SIGN_REQUEST_BY_ID - Get details of a specific sign request [Optional]
BOX_CANCEL_BOX_SIGN_REQUEST - Cancel a pending sign request [Optional]
Key parameters:
sign_request_id: UUID of the sign request
shared_requests: Set true to include requests where user is a collaborator (not owner)
senders: Filter by sender emails (requires shared_requests: true)
limit / marker: Pagination parameters
Pitfalls:
- Requires Box Sign to be enabled for the enterprise account
- Deleted sign files or parent folders cause requests to not appear in listings
- Only the creator can cancel a sign request
- Sign request statuses include:
converting, created, sent, viewed, signed, declined, cancelled, expired, error_converting, error_sending
Common Patterns
ID Resolution
Box uses numeric string IDs for all entities:
- Root folder: Always ID
"0"
- File ID from URL:
https://*.app.box.com/files/123 gives file_id "123"
- Folder ID from URL:
https://*.app.box.com/folder/123 gives folder_id "123"
- Search to ID: Use
BOX_SEARCH_FOR_CONTENT to find items, then extract IDs from results
- ETag: Use
if_match with file's ETag for safe concurrent delete operations
Pagination
Box supports two pagination methods:
- Offset-based: Use
offset + limit (max offset 10000)
- Marker-based: Set
usemarker: true and follow marker from responses (preferred for large datasets)
- Always paginate to completion to avoid partial results
Nested Parameters
Box tools use double underscore notation for nested objects:
parent__id for parent folder reference
lock__access, lock__expires__at, lock__is__download__prevented for file locks
permissions__can__download for download permissions
Known Pitfalls
ID Formats
- All IDs are numeric strings (e.g.,
"123456", not integers)
- Root folder is always
"0"
- File and folder IDs can be extracted from Box web app URLs
Rate Limits
- Box API has per-endpoint rate limits
- Search and list operations should use pagination responsibly
- Bulk operations should include delays between requests
Parameter Quirks
fields parameter changes response shape: when specified, only mini representation + requested fields are returned
- Search requires either
query or mdfilters; both are optional individually but one must be present
BOX_UPDATE_FILE with lock set to null removes the lock (raw API only)
- Metadata query
from field format: enterprise_{enterprise_id}.templateKey or global.templateKey
Permissions
- Deletions fail without sufficient permissions; always handle error responses
- Collaboration roles determine what operations are allowed
- Enterprise settings may restrict certain sharing options
Quick Reference
| Task |
Tool Slug |
Key Params |
| Search content |
BOX_SEARCH_FOR_CONTENT |
query, type, ancestor_folder_ids |
| List folder items |
BOX_LIST_ITEMS_IN_FOLDER |
folder_id, limit, marker |
| Get file info |
BOX_GET_FILE_INFORMATION |
file_id, fields |
| Get folder info |
BOX_GET_FOLDER_INFORMATION |
folder_id, fields |
| Upload file |
BOX_UPLOAD_FILE |
file, parent_id |
| Download file |
BOX_DOWNLOAD_FILE |
file_id |
| Create folder |
BOX_CREATE_FOLDER |
name, parent__id |
| Update folder |
BOX_UPDATE_FOLDER |
folder_id, name, parent |
| Copy folder |
BOX_COPY_FOLDER |
folder_id, parent__id |
| Delete folder |
BOX_DELETE_FOLDER |
folder_id, recursive |
| Permanently delete folder |
BOX_PERMANENTLY_REMOVE_FOLDER |
folder_id |
| Update file |
BOX_UPDATE_FILE |
file_id, name, parent__id |
| Delete file |
BOX_DELETE_FILE |
file_id, if_match |
| List collaborations |
BOX_LIST_FILE_COLLABORATIONS |
file_id |
| Update collaboration |
BOX_UPDATE_COLLABORATION |
collaboration_id, role |
| Get collaboration |
BOX_GET_COLLABORATION |
collaboration_id |
| Query by metadata |
BOX_QUERY_FILES_FOLDERS_BY_METADATA |
from, ancestor_folder_id, query |
| List collections |
BOX_LIST_ALL_COLLECTIONS |
(none) |
| List collection items |
BOX_LIST_COLLECTION_ITEMS |
collection_id |
| List sign requests |
BOX_LIST_BOX_SIGN_REQUESTS |
limit, marker |
| Get sign request |
BOX_GET_BOX_SIGN_REQUEST_BY_ID |
sign_request_id |
| Cancel sign request |
BOX_CANCEL_BOX_SIGN_REQUEST |
sign_request_id |
| Recent items |
BOX_LIST_RECENTLY_ACCESSED_ITEMS |
(none) |
| Create zip download |
BOX_CREATE_ZIP_DOWNLOAD |
item IDs |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Source: sickn33/agentic-awesome-skills → skills/box-automation/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/box-automation/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/box-automation/SKILL.md
1---2name: box-automation3description: Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit.4---5
6
7# Box Automation via Rube MCP
8
9Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit.
10
11## Prerequisites
12
13- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
14- Active Box connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `box`
15- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
16
17## Setup
18
19**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
20
211. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
222. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `box`
233. If connection is not ACTIVE, follow the returned auth link to complete Box OAuth
244. Confirm connection status shows ACTIVE before running any workflows
25
26## Core Workflows
27
28### 1. Upload and Download Files
29
30**When to use**: User wants to upload files to Box or download files from it
31
32**Tool sequence**:
331. `BOX_SEARCH_FOR_CONTENT` - Find the target folder if path is unknown [Prerequisite]
342. `BOX_GET_FOLDER_INFORMATION` - Verify folder exists and get folder_id [Prerequisite]
353. `BOX_LIST_ITEMS_IN_FOLDER` - Browse folder contents and discover file IDs [Optional]
364. `BOX_UPLOAD_FILE` - Upload a file to a specific folder [Required for upload]
375. `BOX_DOWNLOAD_FILE` - Download a file by file_id [Required for download]
386. `BOX_CREATE_ZIP_DOWNLOAD` - Bundle multiple files/folders into a zip [Optional]
39
40**Key parameters**:
41- `parent_id`: Folder ID for upload destination (use `"0"` for root folder)
42- `file`: FileUploadable object with `s3key`, `mimetype`, and `name` for uploads
43- `file_id`: Unique file identifier for downloads
44- `version`: Optional file version ID for downloading specific versions
45- `fields`: Comma-separated list of attributes to return
46
47**Pitfalls**:
48- Uploading to a folder with existing filenames can trigger conflict behavior; decide overwrite vs rename semantics
49- Files over 50MB should use chunk upload APIs (not available via standard tools)
50- The `attributes` part of upload must come before the `file` part or you get HTTP 400 with `metadata_after_file_contents`
51- File IDs and folder IDs are numeric strings extractable from Box web app URLs (e.g., `https://*.app.box.com/files/123` gives file_id `"123"`)
52
53### 2. Search and Browse Content
54
55**When to use**: User wants to find files, folders, or web links by name, content, or metadata
56
57**Tool sequence**:
581. `BOX_SEARCH_FOR_CONTENT` - Full-text search across files, folders, and web links [Required]
592. `BOX_LIST_ITEMS_IN_FOLDER` - Browse contents of a specific folder [Optional]
603. `BOX_GET_FILE_INFORMATION` - Get detailed metadata for a specific file [Optional]
614. `BOX_GET_FOLDER_INFORMATION` - Get detailed metadata for a specific folder [Optional]
625. `BOX_QUERY_FILES_FOLDERS_BY_METADATA` - Search by metadata template values [Optional]
636. `BOX_LIST_RECENTLY_ACCESSED_ITEMS` - List recently accessed items [Optional]
64
65**Key parameters**:
66- `query`: Search string supporting operators (`""` exact match, `AND`, `OR`, `NOT` - uppercase only)
67- `type`: Filter by `"file"`, `"folder"`, or `"web_link"`
68- `ancestor_folder_ids`: Limit search to specific folders (comma-separated IDs)
69- `file_extensions`: Filter by file type (comma-separated, no dots)
70- `content_types`: Search in `"name"`, `"description"`, `"file_content"`, `"comments"`, `"tags"`
71- `created_at_range` / `updated_at_range`: Date filters as comma-separated RFC3339 timestamps
72- `limit`: Results per page (default 30)
73- `offset`: Pagination offset (max 10000)
74- `folder_id`: For `LIST_ITEMS_IN_FOLDER` (use `"0"` for root)
75
76**Pitfalls**:
77- Queries with offset > 10000 are rejected with HTTP 400
78- `BOX_SEARCH_FOR_CONTENT` requires either `query` or `mdfilters` parameter
79- Misconfigured filters can silently omit expected items; validate with small test queries first
80- Boolean operators (`AND`, `OR`, `NOT`) must be uppercase
81- `BOX_LIST_ITEMS_IN_FOLDER` requires pagination via `marker` or `offset`/`usemarker`; partial listings are common
82- Standard folders sort items by type first (folders before files before web links)
83
84### 3. Manage Folders
85
86**When to use**: User wants to create, update, move, copy, or delete folders
87
88**Tool sequence**:
891. `BOX_GET_FOLDER_INFORMATION` - Verify folder exists and check permissions [Prerequisite]
902. `BOX_CREATE_FOLDER` - Create a new folder [Required for create]
913. `BOX_UPDATE_FOLDER` - Rename, move, or update folder settings [Required for update]
924. `BOX_COPY_FOLDER` - Copy a folder to a new location [Optional]
935. `BOX_DELETE_FOLDER` - Move folder to trash [Required for delete]
946. `BOX_PERMANENTLY_REMOVE_FOLDER` - Permanently delete a trashed folder [Optional]
95
96**Key parameters**:
97- `name`: Folder name (no `/`, `\`, trailing spaces, or `.`/`..`)
98- `parent__id`: Parent folder ID (use `"0"` for root)
99- `folder_id`: Target folder ID for operations
100- `parent.id`: Destination folder ID for moves via `BOX_UPDATE_FOLDER`
101- `recursive`: Set `true` to delete non-empty folders
102- `shared_link`: Object with `access`, `password`, `permissions` for creating shared links on folders
103- `description`, `tags`: Optional metadata fields
104
105**Pitfalls**:
106- `BOX_DELETE_FOLDER` moves to trash by default; use `BOX_PERMANENTLY_REMOVE_FOLDER` for permanent deletion
107- Non-empty folders require `recursive: true` for deletion
108- Root folder (ID `"0"`) cannot be copied or deleted
109- Folder names cannot contain `/`, `\`, non-printable ASCII, or trailing spaces
110- Moving folders requires setting `parent.id` via `BOX_UPDATE_FOLDER`
111
112### 4. Share Files and Manage Collaborations
113
114**When to use**: User wants to share files, manage access, or handle collaborations
115
116**Tool sequence**:
1171. `BOX_GET_FILE_INFORMATION` - Get file details and current sharing status [Prerequisite]
1182. `BOX_LIST_FILE_COLLABORATIONS` - List who has access to a file [Required]
1193. `BOX_UPDATE_COLLABORATION` - Change access level or accept/reject invitations [Required]
1204. `BOX_GET_COLLABORATION` - Get details of a specific collaboration [Optional]
1215. `BOX_UPDATE_FILE` - Create shared links, lock files, or update permissions [Optional]
1226. `BOX_UPDATE_FOLDER` - Create shared links on folders [Optional]
123
124**Key parameters**:
125- `collaboration_id`: Unique collaboration identifier
126- `role`: Access level (`"editor"`, `"viewer"`, `"co-owner"`, `"owner"`, `"previewer"`, `"uploader"`, `"viewer uploader"`, `"previewer uploader"`)
127- `status`: `"accepted"`, `"pending"`, or `"rejected"` for collaboration invites
128- `file_id`: File to share or manage
129- `lock__access`: Set to `"lock"` to lock a file
130- `permissions__can__download`: `"company"` or `"open"` for download permissions
131
132**Pitfalls**:
133- Only certain roles can invite collaborators; insufficient permissions cause authorization errors
134- `can_view_path` increases load time for the invitee's "All Files" page; limit to 1000 per user
135- Collaboration expiration requires enterprise admin settings to be enabled
136- Nested parameter names use double underscores (e.g., `lock__access`, `parent__id`)
137
138### 5. Box Sign Requests
139
140**When to use**: User wants to manage document signature requests
141
142**Tool sequence**:
1431. `BOX_LIST_BOX_SIGN_REQUESTS` - List all signature requests [Required]
1442. `BOX_GET_BOX_SIGN_REQUEST_BY_ID` - Get details of a specific sign request [Optional]
1453. `BOX_CANCEL_BOX_SIGN_REQUEST` - Cancel a pending sign request [Optional]
146
147**Key parameters**:
148- `sign_request_id`: UUID of the sign request
149- `shared_requests`: Set `true` to include requests where user is a collaborator (not owner)
150- `senders`: Filter by sender emails (requires `shared_requests: true`)
151- `limit` / `marker`: Pagination parameters
152
153**Pitfalls**:
154- Requires Box Sign to be enabled for the enterprise account
155- Deleted sign files or parent folders cause requests to not appear in listings
156- Only the creator can cancel a sign request
157- Sign request statuses include: `converting`, `created`, `sent`, `viewed`, `signed`, `declined`, `cancelled`, `expired`, `error_converting`, `error_sending`
158
159## Common Patterns
160
161### ID Resolution
162Box uses numeric string IDs for all entities:
163- **Root folder**: Always ID `"0"`
164- **File ID from URL**: `https://*.app.box.com/files/123` gives file_id `"123"`
165- **Folder ID from URL**: `https://*.app.box.com/folder/123` gives folder_id `"123"`
166- **Search to ID**: Use `BOX_SEARCH_FOR_CONTENT` to find items, then extract IDs from results
167- **ETag**: Use `if_match` with file's ETag for safe concurrent delete operations
168
169### Pagination
170Box supports two pagination methods:
171- **Offset-based**: Use `offset` + `limit` (max offset 10000)
172- **Marker-based**: Set `usemarker: true` and follow `marker` from responses (preferred for large datasets)
173- Always paginate to completion to avoid partial results
174
175### Nested Parameters
176Box tools use double underscore notation for nested objects:
177- `parent__id` for parent folder reference
178- `lock__access`, `lock__expires__at`, `lock__is__download__prevented` for file locks
179- `permissions__can__download` for download permissions
180
181## Known Pitfalls
182
183### ID Formats
184- All IDs are numeric strings (e.g., `"123456"`, not integers)
185- Root folder is always `"0"`
186- File and folder IDs can be extracted from Box web app URLs
187
188### Rate Limits
189- Box API has per-endpoint rate limits
190- Search and list operations should use pagination responsibly
191- Bulk operations should include delays between requests
192
193### Parameter Quirks
194- `fields` parameter changes response shape: when specified, only mini representation + requested fields are returned
195- Search requires either `query` or `mdfilters`; both are optional individually but one must be present
196- `BOX_UPDATE_FILE` with `lock` set to `null` removes the lock (raw API only)
197- Metadata query `from` field format: `enterprise_{enterprise_id}.templateKey` or `global.templateKey`
198
199### Permissions
200- Deletions fail without sufficient permissions; always handle error responses
201- Collaboration roles determine what operations are allowed
202- Enterprise settings may restrict certain sharing options
203
204## Quick Reference
205
206| Task | Tool Slug | Key Params |
207|------|-----------|------------|
208| Search content | `BOX_SEARCH_FOR_CONTENT` | `query`, `type`, `ancestor_folder_ids` |
209| List folder items | `BOX_LIST_ITEMS_IN_FOLDER` | `folder_id`, `limit`, `marker` |
210| Get file info | `BOX_GET_FILE_INFORMATION` | `file_id`, `fields` |
211| Get folder info | `BOX_GET_FOLDER_INFORMATION` | `folder_id`, `fields` |
212| Upload file | `BOX_UPLOAD_FILE` | `file`, `parent_id` |
213| Download file | `BOX_DOWNLOAD_FILE` | `file_id` |
214| Create folder | `BOX_CREATE_FOLDER` | `name`, `parent__id` |
215| Update folder | `BOX_UPDATE_FOLDER` | `folder_id`, `name`, `parent` |
216| Copy folder | `BOX_COPY_FOLDER` | `folder_id`, `parent__id` |
217| Delete folder | `BOX_DELETE_FOLDER` | `folder_id`, `recursive` |
218| Permanently delete folder | `BOX_PERMANENTLY_REMOVE_FOLDER` | folder_id |
219| Update file | `BOX_UPDATE_FILE` | `file_id`, `name`, `parent__id` |
220| Delete file | `BOX_DELETE_FILE` | `file_id`, `if_match` |
221| List collaborations | `BOX_LIST_FILE_COLLABORATIONS` | `file_id` |
222| Update collaboration | `BOX_UPDATE_COLLABORATION` | `collaboration_id`, `role` |
223| Get collaboration | `BOX_GET_COLLABORATION` | `collaboration_id` |
224| Query by metadata | `BOX_QUERY_FILES_FOLDERS_BY_METADATA` | `from`, `ancestor_folder_id`, `query` |
225| List collections | `BOX_LIST_ALL_COLLECTIONS` | (none) |
226| List collection items | `BOX_LIST_COLLECTION_ITEMS` | `collection_id` |
227| List sign requests | `BOX_LIST_BOX_SIGN_REQUESTS` | `limit`, `marker` |
228| Get sign request | `BOX_GET_BOX_SIGN_REQUEST_BY_ID` | `sign_request_id` |
229| Cancel sign request | `BOX_CANCEL_BOX_SIGN_REQUEST` | `sign_request_id` |
230| Recent items | `BOX_LIST_RECENTLY_ACCESSED_ITEMS` | (none) |
231| Create zip download | `BOX_CREATE_ZIP_DOWNLOAD` | item IDs |
232
233## When to Use
234This skill is applicable to execute the workflow or actions described in the overview.
235
236## Limitations
237- Use this skill only when the task clearly matches the scope described above.
238- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
239- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
240
241---
242
243**Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/box-automation/SKILL.md`
244
245**Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/box-automation/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/box-automation/SKILL.md`