القائمة
Discovers and classifies tax documents in Box using the Box CLI.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when working with the Anthropic Skills API for document creation (pptx, xlsx, docx, pdf) via code execution containers.
Use this skill for all Box operations — uploading, downloading, searching, and managing files and folders in Box. Uses the Box CLI (@box/cli) via Bash commands with a developer token.
Use this skill when working with the Box API, Box Content Cloud, or Box Node SDK (v10/v4). This includes file/folder operations, authentication (OAuth 2.0, JWT, Client Credentials, Developer Token), uploads, downloads, metadata, collaborations, and any Box platform integration tasks. Trigger when the user mentions Box, Box API, Box SDK, or box-node-sdk.
Manages Box sharing permissions, Box Sign requests, and task assignments.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Downloads and extracts structured data from tax documents.
| name | explorer |
| description | Discovers and classifies tax documents in Box using the Box CLI. |
Find and classify tax documents using npx @box/cli. Always pass --token $BOX_DEVELOPER_TOKEN --json.
npx @box/cli search "W-2" --token $BOX_DEVELOPER_TOKEN --jsonnpx @box/cli search "receipt" --type file --token $BOX_DEVELOPER_TOKEN --jsonnpx @box/cli folders:items FOLDER_ID --token $BOX_DEVELOPER_TOKEN --jsonnpx @box/cli files:get FILE_ID --token $BOX_DEVELOPER_TOKEN --jsonSearch syntax: The QUERY is a single positional argument — always quote it. There is no OR operator. To search for multiple terms, run separate commands (e.g. one for "receipt", one for "invoice"). Useful flags: --type file, --file-extensions pdf,png, --ancestor-folder-ids FOLDER_ID, --limit N.
Classify each document into: W-2, 1099-NEC, 1099-INT, 1099-DIV, 1099-MISC, 1099-R, 1098, Receipt, Invoice, Bank Statement, Other.
Structure your response by category. For each category, write a short heading, then for EACH file immediately output its own JSON code fence. NEVER list files as plain text bullet points. NEVER put all files in one JSON array at the end.
Pattern to follow for EVERY file you mention:
**W-2 Forms (Employment Income):**
W-2 from Acme Robotics (02_Income folder):
```json
[{ "fileId": "111", "fileName": "W2_Acme.pdf", "type": "W-2", "boxPath": "Tax Docs/02_Income" }]
```
**1099-NEC Forms:**
1099-NEC from Client X Media:
```json
[{ "fileId": "222", "fileName": "1099NEC_ClientX.pdf", "type": "1099-NEC", "boxPath": "Tax Docs/02_Income" }]
```
Each JSON code fence becomes a clickable file card in the UI. If you group them all together, they bunch up at the bottom instead of appearing next to their descriptions.
If a command fails, run it with --help to check syntax, gather context, then retry.