[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMM9PC28YH1EK2F3FQQV2C":3,"skill-same:01M7CMM9PC28YH1EK2F3FQQV2C":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CMM9PC28YH1EK2F3FQQV2C","one-drive-automation",null,"Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fone-drive-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: one-drive-automation\ndescription: \"Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# OneDrive Automation via Rube MCP\n\nAutomate OneDrive operations including file upload\u002Fdownload, search, folder management, sharing links, permissions management, and drive browsing through Composio's OneDrive toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active OneDrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`\n3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Browse Files\n\n**When to use**: User wants to find files or browse folder contents in OneDrive\n\n**Tool sequence**:\n1. `ONE_DRIVE_GET_DRIVE` - Verify drive access and get drive details [Prerequisite]\n2. `ONE_DRIVE_SEARCH_ITEMS` - Keyword search across filenames, metadata, and content [Required]\n3. `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` - List all items in the root of a drive [Optional]\n4. `ONE_DRIVE_GET_ITEM` - Get detailed metadata for a specific item, expand children [Optional]\n5. `ONE_DRIVE_ONEDRIVE_FIND_FILE` - Find a specific file by exact name in a folder [Optional]\n6. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Find a specific folder by name [Optional]\n7. `ONE_DRIVE_LIST_DRIVES` - List all accessible drives [Optional]\n\n**Key parameters**:\n- `q`: Search query (plain keywords only, NOT KQL syntax)\n- `search_scope`: `\"root\"` (folder hierarchy) or `\"drive\"` (includes shared items)\n- `top`: Max items per page (default 200)\n- `skip_token`: Pagination token from `@odata.nextLink`\n- `select`: Comma-separated fields to return (e.g., `\"id,name,webUrl,size\"`)\n- `orderby`: Sort order (e.g., `\"name asc\"`, `\"name desc\"`)\n- `item_id`: Item ID for `GET_ITEM`\n- `expand_relations`: Array like `[\"children\"]` or `[\"thumbnails\"]` for `GET_ITEM`\n- `user_id`: `\"me\"` (default) or specific user ID\u002Femail\n\n**Pitfalls**:\n- `ONE_DRIVE_SEARCH_ITEMS` does NOT support KQL operators (`folder:`, `file:`, `filetype:`, `path:`); these are treated as literal text\n- Wildcard characters (`*`, `?`) are NOT supported and are auto-removed; use file extension keywords instead (e.g., `\"pdf\"` not `\"*.pdf\"`)\n- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` returns only root-level contents; use recursive `ONE_DRIVE_GET_ITEM` with `expand_relations: [\"children\"]` for deeper levels\n- Large folders paginate; always follow `skip_token` \u002F `@odata.nextLink` until exhausted\n- Some drive ID formats may return \"ObjectHandle is Invalid\" errors due to Microsoft Graph API limitations\n\n### 2. Upload and Download Files\n\n**When to use**: User wants to upload files to OneDrive or download files from it\n\n**Tool sequence**:\n1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the target folder [Prerequisite]\n2. `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` - Upload a file to a specified folder [Required for upload]\n3. `ONE_DRIVE_DOWNLOAD_FILE` - Download a file by item ID [Required for download]\n4. `ONE_DRIVE_GET_ITEM` - Get file details before download [Optional]\n\n**Key parameters**:\n- `file`: FileUploadable object with `s3key`, `mimetype`, and `name` for uploads\n- `folder`: Destination path (e.g., `\"\u002FDocuments\u002FReports\"`) or folder ID for uploads\n- `item_id`: File's unique identifier for downloads\n- `file_name`: Desired filename with extension for downloads\n- `drive_id`: Specific drive ID (for SharePoint or OneDrive for Business)\n- `user_id`: `\"me\"` (default) or specific user identifier\n\n**Pitfalls**:\n- Upload automatically renames on conflict (no overwrite option by default)\n- Large files are automatically handled via chunking\n- `drive_id` overrides `user_id` when both are provided\n- Item IDs vary by platform: OneDrive for Business uses `01...` prefix, OneDrive Personal uses `HASH!NUMBER` format\n- Item IDs are case-sensitive; use exactly as returned from API\n\n### 3. Share Files and Manage Permissions\n\n**When to use**: User wants to share files\u002Ffolders or manage who has access\n\n**Tool sequence**:\n1. `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the item [Prerequisite]\n2. `ONE_DRIVE_GET_ITEM_PERMISSIONS` - Check current permissions [Prerequisite]\n3. `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` - Grant access to specific users [Required]\n4. `ONE_DRIVE_CREATE_LINK` - Create a shareable link [Optional]\n5. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Update item metadata [Optional]\n\n**Key parameters**:\n- `item_id`: The file or folder to share\n- `recipients`: Array of objects with `email` or `object_id`\n- `roles`: Array with `\"read\"` or `\"write\"`\n- `send_invitation`: `true` to send notification email, `false` for silent permission grant\n- `require_sign_in`: `true` to require authentication to access\n- `message`: Custom message for invitation (max 2000 characters)\n- `expiration_date_time`: ISO 8601 date for permission expiry\n- `retain_inherited_permissions`: `true` (default) to keep existing inherited permissions\n\n**Pitfalls**:\n- Using wrong `item_id` with `INVITE_USER_TO_DRIVE_ITEM` changes permissions on unintended items; always verify first\n- Write or higher roles are impactful; get explicit user confirmation before granting\n- `GET_ITEM_PERMISSIONS` returns inherited and owner entries; do not assume response only reflects recent changes\n- `permissions` cannot be expanded via `ONE_DRIVE_GET_ITEM`; use the separate permissions endpoint\n- At least one of `require_sign_in` or `send_invitation` must be `true`\n\n### 4. Manage Folders (Create, Move, Delete, Copy)\n\n**When to use**: User wants to create, move, rename, delete, or copy files and folders\n\n**Tool sequence**:\n1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate source and destination folders [Prerequisite]\n2. `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` - Create a new folder [Required for create]\n3. `ONE_DRIVE_MOVE_ITEM` - Move a file or folder to a new location [Required for move]\n4. `ONE_DRIVE_COPY_ITEM` - Copy a file or folder (async operation) [Required for copy]\n5. `ONE_DRIVE_DELETE_ITEM` - Move item to recycle bin [Required for delete]\n6. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Rename or update item properties [Optional]\n\n**Key parameters**:\n- `name`: Folder name for creation or new name for rename\u002Fcopy\n- `parent_folder`: Path (e.g., `\"\u002FDocuments\u002FReports\"`) or folder ID for creation\n- `itemId`: Item to move\n- `parentReference`: Object with `id` (destination folder ID) for moves: `{\"id\": \"folder_id\"}`\n- `item_id`: Item to copy or delete\n- `parent_reference`: Object with `id` and optional `driveId` for copy destination\n- `@microsoft.graph.conflictBehavior`: `\"fail\"`, `\"replace\"`, or `\"rename\"` for copies\n- `if_match`: ETag for optimistic concurrency on deletes\n\n**Pitfalls**:\n- `ONE_DRIVE_MOVE_ITEM` does NOT support cross-drive moves; use `ONE_DRIVE_COPY_ITEM` for cross-drive transfers\n- `parentReference` for moves requires folder ID (not folder name); resolve with `ONEDRIVE_FIND_FOLDER` first\n- `ONE_DRIVE_COPY_ITEM` is asynchronous; response provides a URL to monitor progress\n- `ONE_DRIVE_DELETE_ITEM` moves to recycle bin, not permanent deletion\n- Folder creation auto-renames on conflict (e.g., \"New Folder\" becomes \"New Folder 1\")\n- Provide either `name` or `parent_reference` (or both) for `ONE_DRIVE_COPY_ITEM`\n\n### 5. Track Changes and Drive Information\n\n**When to use**: User wants to monitor changes or get drive\u002Fquota information\n\n**Tool sequence**:\n1. `ONE_DRIVE_GET_DRIVE` - Get drive properties and metadata [Required]\n2. `ONE_DRIVE_GET_QUOTA` - Check storage quota (total, used, remaining) [Optional]\n3. `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` - Track changes in SharePoint site drives [Optional]\n4. `ONE_DRIVE_GET_ITEM_VERSIONS` - Get version history of a file [Optional]\n\n**Key parameters**:\n- `drive_id`: Drive identifier (or `\"me\"` for personal drive)\n- `site_id`: SharePoint site identifier for delta tracking\n- `token`: Delta token (`\"latest\"` for current state, URL for next page, or timestamp)\n- `item_id`: File ID for version history\n\n**Pitfalls**:\n- Delta queries are only available for SharePoint site drives via `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA`\n- Token `\"latest\"` returns current delta token without items (useful as starting point)\n- Deep or large drives can take several minutes to crawl; use batching and resume logic\n\n## Common Patterns\n\n### ID Resolution\n- **User**: Use `\"me\"` for authenticated user or specific user email\u002FGUID\n- **Item ID from find**: Use `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` to get item IDs\n- **Item ID from search**: Extract from `ONE_DRIVE_SEARCH_ITEMS` results\n- **Drive ID**: Use `ONE_DRIVE_LIST_DRIVES` or `ONE_DRIVE_GET_DRIVE` to discover drives\n- **Folder path to ID**: Use `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` with path, then extract ID from response\n\nID formats vary by platform:\n- OneDrive for Business\u002FSharePoint: `01NKDM7HMOJTVYMDOSXFDK2QJDXCDI3WUK`\n- OneDrive Personal: `D4648F06C91D9D3D!54927`\n\n### Pagination\nOneDrive uses token-based pagination:\n- Follow `@odata.nextLink` or `skip_token` until no more pages\n- Set `top` for page size (varies by endpoint)\n- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` auto-handles pagination internally\n- Aggressive parallel requests can trigger HTTP 429; honor `Retry-After` headers\n\n### Path vs ID\nMost OneDrive tools accept either paths or IDs:\n- **Paths**: Start with `\u002F` (e.g., `\"\u002FDocuments\u002FReports\"`)\n- **IDs**: Use unique item identifiers from API responses\n- **Item paths for permissions**: Use `:\u002Fpath\u002Fto\u002Fitem:\u002F` format\n\n## Known Pitfalls\n\n### ID Formats\n- Item IDs are case-sensitive and platform-specific\n- Never use web URLs, sharing links, or manually constructed identifiers as item IDs\n- Always use IDs exactly as returned from Microsoft Graph API\n\n### Rate Limits\n- Aggressive parallel `ONE_DRIVE_GET_ITEM` calls can trigger HTTP 429 Too Many Requests\n- Honor `Retry-After` headers and implement throttling\n- Deep drive crawls should use batching with delays\n\n### Search Limitations\n- No KQL support; use plain keywords only\n- No wildcard characters; use extension keywords (e.g., `\"pdf\"` not `\"*.pdf\"`)\n- No path-based filtering in search; use folder listing instead\n- `q='*'` wildcard-only queries return HTTP 400 invalidRequest\n\n### Parameter Quirks\n- `drive_id` overrides `user_id` when both are provided\n- `permissions` cannot be expanded via `GET_ITEM`; use dedicated permissions endpoint\n- Move operations require folder IDs in `parentReference`, not folder names\n- Copy operations are asynchronous; response provides monitoring URL\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search files | `ONE_DRIVE_SEARCH_ITEMS` | `q`, `search_scope`, `top` |\n| List root items | `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` | `user_id`, `select`, `top` |\n| Get item details | `ONE_DRIVE_GET_ITEM` | `item_id`, `expand_relations` |\n| Find file by name | `ONE_DRIVE_ONEDRIVE_FIND_FILE` | `name`, `folder` |\n| Find folder by name | `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` | `name`, `folder` |\n| Upload file | `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` | `file`, `folder` |\n| Download file | `ONE_DRIVE_DOWNLOAD_FILE` | `item_id`, `file_name` |\n| Create folder | `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` | `name`, `parent_folder` |\n| Move item | `ONE_DRIVE_MOVE_ITEM` | `itemId`, `parentReference` |\n| Copy item | `ONE_DRIVE_COPY_ITEM` | `item_id`, `parent_reference`, `name` |\n| Delete item | `ONE_DRIVE_DELETE_ITEM` | `item_id` |\n| Share with users | `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` | `item_id`, `recipients`, `roles` |\n| Create share link | `ONE_DRIVE_CREATE_LINK` | `item_id`, link type |\n| Get permissions | `ONE_DRIVE_GET_ITEM_PERMISSIONS` | `item_id` |\n| Update metadata | `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` | `item_id`, fields |\n| Get drive info | `ONE_DRIVE_GET_DRIVE` | `drive_id` |\n| List drives | `ONE_DRIVE_LIST_DRIVES` | user\u002Fgroup\u002Fsite scope |\n| Get quota | `ONE_DRIVE_GET_QUOTA` | (none) |\n| Track changes | `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` | `site_id`, `token` |\n| Version history | `ONE_DRIVE_GET_ITEM_VERSIONS` | `item_id` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# OneDrive Automation via Rube MCP\n\nAutomate OneDrive operations including file upload\u002Fdownload, search, folder management, sharing links, permissions management, and drive browsing through Composio's OneDrive toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active OneDrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`\n3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Browse Files\n\n**When to use**: User wants to find files or browse folder contents in OneDrive\n\n**Tool sequence**:\n1. `ONE_DRIVE_GET_DRIVE` - Verify drive access and get drive details [Prerequisite]\n2. `ONE_DRIVE_SEARCH_ITEMS` - Keyword search across filenames, metadata, and content [Required]\n3. `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` - List all items in the root of a drive [Optional]\n4. `ONE_DRIVE_GET_ITEM` - Get detailed metadata for a specific item, expand children [Optional]\n5. `ONE_DRIVE_ONEDRIVE_FIND_FILE` - Find a specific file by exact name in a folder [Optional]\n6. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Find a specific folder by name [Optional]\n7. `ONE_DRIVE_LIST_DRIVES` - List all accessible drives [Optional]\n\n**Key parameters**:\n- `q`: Search query (plain keywords only, NOT KQL syntax)\n- `search_scope`: `\"root\"` (folder hierarchy) or `\"drive\"` (includes shared items)\n- `top`: Max items per page (default 200)\n- `skip_token`: Pagination token from `@odata.nextLink`\n- `select`: Comma-separated fields to return (e.g., `\"id,name,webUrl,size\"`)\n- `orderby`: Sort order (e.g., `\"name asc\"`, `\"name desc\"`)\n- `item_id`: Item ID for `GET_ITEM`\n- `expand_relations`: Array like `[\"children\"]` or `[\"thumbnails\"]` for `GET_ITEM`\n- `user_id`: `\"me\"` (default) or specific user ID\u002Femail\n\n**Pitfalls**:\n- `ONE_DRIVE_SEARCH_ITEMS` does NOT support KQL operators (`folder:`, `file:`, `filetype:`, `path:`); these are treated as literal text\n- Wildcard characters (`*`, `?`) are NOT supported and are auto-removed; use file extension keywords instead (e.g., `\"pdf\"` not `\"*.pdf\"`)\n- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` returns only root-level contents; use recursive `ONE_DRIVE_GET_ITEM` with `expand_relations: [\"children\"]` for deeper levels\n- Large folders paginate; always follow `skip_token` \u002F `@odata.nextLink` until exhausted\n- Some drive ID formats may return \"ObjectHandle is Invalid\" errors due to Microsoft Graph API limitations\n\n### 2. Upload and Download Files\n\n**When to use**: User wants to upload files to OneDrive or download files from it\n\n**Tool sequence**:\n1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the target folder [Prerequisite]\n2. `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` - Upload a file to a specified folder [Required for upload]\n3. `ONE_DRIVE_DOWNLOAD_FILE` - Download a file by item ID [Required for download]\n4. `ONE_DRIVE_GET_ITEM` - Get file details before download [Optional]\n\n**Key parameters**:\n- `file`: FileUploadable object with `s3key`, `mimetype`, and `name` for uploads\n- `folder`: Destination path (e.g., `\"\u002FDocuments\u002FReports\"`) or folder ID for uploads\n- `item_id`: File's unique identifier for downloads\n- `file_name`: Desired filename with extension for downloads\n- `drive_id`: Specific drive ID (for SharePoint or OneDrive for Business)\n- `user_id`: `\"me\"` (default) or specific user identifier\n\n**Pitfalls**:\n- Upload automatically renames on conflict (no overwrite option by default)\n- Large files are automatically handled via chunking\n- `drive_id` overrides `user_id` when both are provided\n- Item IDs vary by platform: OneDrive for Business uses `01...` prefix, OneDrive Personal uses `HASH!NUMBER` format\n- Item IDs are case-sensitive; use exactly as returned from API\n\n### 3. Share Files and Manage Permissions\n\n**When to use**: User wants to share files\u002Ffolders or manage who has access\n\n**Tool sequence**:\n1. `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the item [Prerequisite]\n2. `ONE_DRIVE_GET_ITEM_PERMISSIONS` - Check current permissions [Prerequisite]\n3. `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` - Grant access to specific users [Required]\n4. `ONE_DRIVE_CREATE_LINK` - Create a shareable link [Optional]\n5. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Update item metadata [Optional]\n\n**Key parameters**:\n- `item_id`: The file or folder to share\n- `recipients`: Array of objects with `email` or `object_id`\n- `roles`: Array with `\"read\"` or `\"write\"`\n- `send_invitation`: `true` to send notification email, `false` for silent permission grant\n- `require_sign_in`: `true` to require authentication to access\n- `message`: Custom message for invitation (max 2000 characters)\n- `expiration_date_time`: ISO 8601 date for permission expiry\n- `retain_inherited_permissions`: `true` (default) to keep existing inherited permissions\n\n**Pitfalls**:\n- Using wrong `item_id` with `INVITE_USER_TO_DRIVE_ITEM` changes permissions on unintended items; always verify first\n- Write or higher roles are impactful; get explicit user confirmation before granting\n- `GET_ITEM_PERMISSIONS` returns inherited and owner entries; do not assume response only reflects recent changes\n- `permissions` cannot be expanded via `ONE_DRIVE_GET_ITEM`; use the separate permissions endpoint\n- At least one of `require_sign_in` or `send_invitation` must be `true`\n\n### 4. Manage Folders (Create, Move, Delete, Copy)\n\n**When to use**: User wants to create, move, rename, delete, or copy files and folders\n\n**Tool sequence**:\n1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate source and destination folders [Prerequisite]\n2. `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` - Create a new folder [Required for create]\n3. `ONE_DRIVE_MOVE_ITEM` - Move a file or folder to a new location [Required for move]\n4. `ONE_DRIVE_COPY_ITEM` - Copy a file or folder (async operation) [Required for copy]\n5. `ONE_DRIVE_DELETE_ITEM` - Move item to recycle bin [Required for delete]\n6. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Rename or update item properties [Optional]\n\n**Key parameters**:\n- `name`: Folder name for creation or new name for rename\u002Fcopy\n- `parent_folder`: Path (e.g., `\"\u002FDocuments\u002FReports\"`) or folder ID for creation\n- `itemId`: Item to move\n- `parentReference`: Object with `id` (destination folder ID) for moves: `{\"id\": \"folder_id\"}`\n- `item_id`: Item to copy or delete\n- `parent_reference`: Object with `id` and optional `driveId` for copy destination\n- `@microsoft.graph.conflictBehavior`: `\"fail\"`, `\"replace\"`, or `\"rename\"` for copies\n- `if_match`: ETag for optimistic concurrency on deletes\n\n**Pitfalls**:\n- `ONE_DRIVE_MOVE_ITEM` does NOT support cross-drive moves; use `ONE_DRIVE_COPY_ITEM` for cross-drive transfers\n- `parentReference` for moves requires folder ID (not folder name); resolve with `ONEDRIVE_FIND_FOLDER` first\n- `ONE_DRIVE_COPY_ITEM` is asynchronous; response provides a URL to monitor progress\n- `ONE_DRIVE_DELETE_ITEM` moves to recycle bin, not permanent deletion\n- Folder creation auto-renames on conflict (e.g., \"New Folder\" becomes \"New Folder 1\")\n- Provide either `name` or `parent_reference` (or both) for `ONE_DRIVE_COPY_ITEM`\n\n### 5. Track Changes and Drive Information\n\n**When to use**: User wants to monitor changes or get drive\u002Fquota information\n\n**Tool sequence**:\n1. `ONE_DRIVE_GET_DRIVE` - Get drive properties and metadata [Required]\n2. `ONE_DRIVE_GET_QUOTA` - Check storage quota (total, used, remaining) [Optional]\n3. `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` - Track changes in SharePoint site drives [Optional]\n4. `ONE_DRIVE_GET_ITEM_VERSIONS` - Get version history of a file [Optional]\n\n**Key parameters**:\n- `drive_id`: Drive identifier (or `\"me\"` for personal drive)\n- `site_id`: SharePoint site identifier for delta tracking\n- `token`: Delta token (`\"latest\"` for current state, URL for next page, or timestamp)\n- `item_id`: File ID for version history\n\n**Pitfalls**:\n- Delta queries are only available for SharePoint site drives via `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA`\n- Token `\"latest\"` returns current delta token without items (useful as starting point)\n- Deep or large drives can take several minutes to crawl; use batching and resume logic\n\n## Common Patterns\n\n### ID Resolution\n- **User**: Use `\"me\"` for authenticated user or specific user email\u002FGUID\n- **Item ID from find**: Use `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` to get item IDs\n- **Item ID from search**: Extract from `ONE_DRIVE_SEARCH_ITEMS` results\n- **Drive ID**: Use `ONE_DRIVE_LIST_DRIVES` or `ONE_DRIVE_GET_DRIVE` to discover drives\n- **Folder path to ID**: Use `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` with path, then extract ID from response\n\nID formats vary by platform:\n- OneDrive for Business\u002FSharePoint: `01NKDM7HMOJTVYMDOSXFDK2QJDXCDI3WUK`\n- OneDrive Personal: `D4648F06C91D9D3D!54927`\n\n### Pagination\nOneDrive uses token-based pagination:\n- Follow `@odata.nextLink` or `skip_token` until no more pages\n- Set `top` for page size (varies by endpoint)\n- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` auto-handles pagination internally\n- Aggressive parallel requests can trigger HTTP 429; honor `Retry-After` headers\n\n### Path vs ID\nMost OneDrive tools accept either paths or IDs:\n- **Paths**: Start with `\u002F` (e.g., `\"\u002FDocuments\u002FReports\"`)\n- **IDs**: Use unique item identifiers from API responses\n- **Item paths for permissions**: Use `:\u002Fpath\u002Fto\u002Fitem:\u002F` format\n\n## Known Pitfalls\n\n### ID Formats\n- Item IDs are case-sensitive and platform-specific\n- Never use web URLs, sharing links, or manually constructed identifiers as item IDs\n- Always use IDs exactly as returned from Microsoft Graph API\n\n### Rate Limits\n- Aggressive parallel `ONE_DRIVE_GET_ITEM` calls can trigger HTTP 429 Too Many Requests\n- Honor `Retry-After` headers and implement throttling\n- Deep drive crawls should use batching with delays\n\n### Search Limitations\n- No KQL support; use plain keywords only\n- No wildcard characters; use extension keywords (e.g., `\"pdf\"` not `\"*.pdf\"`)\n- No path-based filtering in search; use folder listing instead\n- `q='*'` wildcard-only queries return HTTP 400 invalidRequest\n\n### Parameter Quirks\n- `drive_id` overrides `user_id` when both are provided\n- `permissions` cannot be expanded via `GET_ITEM`; use dedicated permissions endpoint\n- Move operations require folder IDs in `parentReference`, not folder names\n- Copy operations are asynchronous; response provides monitoring URL\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search files | `ONE_DRIVE_SEARCH_ITEMS` | `q`, `search_scope`, `top` |\n| List root items | `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` | `user_id`, `select`, `top` |\n| Get item details | `ONE_DRIVE_GET_ITEM` | `item_id`, `expand_relations` |\n| Find file by name | `ONE_DRIVE_ONEDRIVE_FIND_FILE` | `name`, `folder` |\n| Find folder by name | `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` | `name`, `folder` |\n| Upload file | `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` | `file`, `folder` |\n| Download file | `ONE_DRIVE_DOWNLOAD_FILE` | `item_id`, `file_name` |\n| Create folder | `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` | `name`, `parent_folder` |\n| Move item | `ONE_DRIVE_MOVE_ITEM` | `itemId`, `parentReference` |\n| Copy item | `ONE_DRIVE_COPY_ITEM` | `item_id`, `parent_reference`, `name` |\n| Delete item | `ONE_DRIVE_DELETE_ITEM` | `item_id` |\n| Share with users | `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` | `item_id`, `recipients`, `roles` |\n| Create share link | `ONE_DRIVE_CREATE_LINK` | `item_id`, link type |\n| Get permissions | `ONE_DRIVE_GET_ITEM_PERMISSIONS` | `item_id` |\n| Update metadata | `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` | `item_id`, fields |\n| Get drive info | `ONE_DRIVE_GET_DRIVE` | `drive_id` |\n| List drives | `ONE_DRIVE_LIST_DRIVES` | user\u002Fgroup\u002Fsite scope |\n| Get quota | `ONE_DRIVE_GET_QUOTA` | (none) |\n| Track changes | `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` | `site_id`, `token` |\n| Version history | `ONE_DRIVE_GET_ITEM_VERSIONS` | `item_id` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fone-drive-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill one-drive-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill one-drive-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill one-drive-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fone-drive-automation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]