skill-library-mcp 1.0.0

package/skills/onboarding-cro/SKILL.md

@@ -0,0 +1,433 @@
+---
+name: onboarding-cro
+description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
+---
+
+# Onboarding CRO
+
+You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
+
+## Initial Assessment
+
+Before providing recommendations, understand:
+
+1. **Product Context**
+   - What type of product? (SaaS tool, marketplace, app, etc.)
+   - B2B or B2C?
+   - What's the core value proposition?
+
+2. **Activation Definition**
+   - What's the "aha moment" for your product?
+   - What action indicates a user "gets it"?
+   - What's your current activation rate?
+
+3. **Current State**
+   - What happens immediately after signup?
+   - Is there an existing onboarding flow?
+   - Where do users currently drop off?
+
+---
+
+## Core Principles
+
+### 1. Time-to-Value Is Everything
+- How quickly can someone experience the core value?
+- Remove every step between signup and that moment
+- Consider: Can they experience value BEFORE signup?
+
+### 2. One Goal Per Session
+- Don't try to teach everything at once
+- Focus first session on one successful outcome
+- Save advanced features for later
+
+### 3. Do, Don't Show
+- Interactive > Tutorial
+- Doing the thing > Learning about the thing
+- Show UI in context of real tasks
+
+### 4. Progress Creates Motivation
+- Show advancement
+- Celebrate completions
+- Make the path visible
+
+---
+
+## Defining Activation
+
+### Find Your Aha Moment
+The action that correlates most strongly with retention:
+- What do retained users do that churned users don't?
+- What's the earliest indicator of future engagement?
+- What action demonstrates they "got it"?
+
+**Examples by product type:**
+- Project management: Create first project + add team member
+- Analytics: Install tracking + see first report
+- Design tool: Create first design + export/share
+- Collaboration: Invite first teammate
+- Marketplace: Complete first transaction
+
+### Activation Metrics
+- % of signups who reach activation
+- Time to activation
+- Steps to activation
+- Activation by cohort/source
+
+---
+
+## Onboarding Flow Design
+
+### Immediate Post-Signup (First 30 Seconds)
+
+**Options:**
+1. **Product-first**: Drop directly into product
+   - Best for: Simple products, B2C, mobile apps
+   - Risk: Blank slate overwhelm
+
+2. **Guided setup**: Short wizard to configure
+   - Best for: Products needing personalization
+   - Risk: Adds friction before value
+
+3. **Value-first**: Show outcome immediately
+   - Best for: Products with demo data or samples
+   - Risk: May not feel "real"
+
+**Whatever you choose:**
+- Clear single next action
+- No dead ends
+- Progress indication if multi-step
+
+### Onboarding Checklist Pattern
+
+**When to use:**
+- Multiple setup steps required
+- Product has several features to discover
+- Self-serve B2B products
+
+**Best practices:**
+- 3-7 items (not overwhelming)
+- Order by value (most impactful first)
+- Start with quick wins
+- Progress bar/completion %
+- Celebration on completion
+- Dismiss option (don't trap users)
+
+**Checklist item structure:**
+- Clear action verb
+- Benefit hint
+- Estimated time
+- Quick-start capability
+
+Example:
+```
+☐ Connect your first data source (2 min)
+  Get real-time insights from your existing tools
+  [Connect Now]
+```
+
+### Empty States
+
+Empty states are onboarding opportunities, not dead ends.
+
+**Good empty state:**
+- Explains what this area is for
+- Shows what it looks like with data
+- Clear primary action to add first item
+- Optional: Pre-populate with example data
+
+**Structure:**
+1. Illustration or preview
+2. Brief explanation of value
+3. Primary CTA to add first item
+4. Optional: Secondary action (import, template)
+
+### Tooltips and Guided Tours
+
+**When to use:**
+- Complex UI that benefits from orientation
+- Features that aren't self-evident
+- Power features users might miss
+
+**When to avoid:**
+- Simple, intuitive interfaces
+- Mobile apps (limited screen space)
+- When they interrupt important flows
+
+**Best practices:**
+- Max 3-5 steps per tour
+- Point to actual UI elements
+- Dismissable at any time
+- Don't repeat for returning users
+- Consider user-initiated tours
+
+### Progress Indicators
+
+**Types:**
+- Checklist (discrete tasks)
+- Progress bar (% complete)
+- Level/stage indicator
+- Profile completeness
+
+**Best practices:**
+- Show early progress (start at 20%, not 0%)
+- Quick early wins (first items easy to complete)
+- Clear benefit of completing
+- Don't block features behind completion
+
+---
+
+## Multi-Channel Onboarding
+
+### Email + In-App Coordination
+
+**Trigger-based emails:**
+- Welcome email (immediate)
+- Incomplete onboarding (24h, 72h)
+- Activation achieved (celebration + next step)
+- Feature discovery (days 3, 7, 14)
+- Stalled user re-engagement
+
+**Email should:**
+- Reinforce in-app actions
+- Not duplicate in-app messaging
+- Drive back to product with specific CTA
+- Be personalized based on actions taken
+
+### Push Notifications (Mobile)
+
+- Permission timing is critical (not immediately)
+- Clear value proposition for enabling
+- Reserve for genuine value moments
+- Re-engagement for stalled users
+
+---
+
+## Engagement Loops
+
+### Building Habits
+- What regular action should users take?
+- What trigger can prompt return?
+- What reward reinforces the behavior?
+
+**Loop structure:**
+Trigger → Action → Variable Reward → Investment
+
+**Examples:**
+- Trigger: Email digest of activity
+- Action: Log in to respond
+- Reward: Social engagement, progress, achievement
+- Investment: Add more data, connections, content
+
+### Milestone Celebrations
+- Acknowledge meaningful achievements
+- Show progress relative to journey
+- Suggest next milestone
+- Shareable moments (social proof generation)
+
+---
+
+## Handling Stalled Users
+
+### Detection
+- Define "stalled" criteria (X days inactive, incomplete setup)
+- Monitor at cohort level
+- Track recovery rate
+
+### Re-engagement Tactics
+1. **Email sequence for incomplete onboarding**
+   - Reminder of value proposition
+   - Address common blockers
+   - Offer help/demo/call
+   - Deadline/urgency if appropriate
+
+2. **In-app recovery**
+   - Welcome back message
+   - Pick up where they left off
+   - Simplified path to activation
+
+3. **Human touch**
+   - For high-value accounts: personal outreach
+   - Offer live walkthrough
+   - Ask what's blocking them
+
+---
+
+## Measurement
+
+### Key Metrics
+- **Activation rate**: % reaching activation event
+- **Time to activation**: How long to first value
+- **Onboarding completion**: % completing setup
+- **Day 1/7/30 retention**: Return rate by timeframe
+- **Feature adoption**: Which features get used
+
+### Funnel Analysis
+Track drop-off at each step:
+```
+Signup → Step 1 → Step 2 → Activation → Retention
+100%      80%       60%       40%         25%
+```
+
+Identify biggest drops and focus there.
+
+---
+
+## Output Format
+
+### Onboarding Audit
+For each issue:
+- **Finding**: What's happening
+- **Impact**: Why it matters
+- **Recommendation**: Specific fix
+- **Priority**: High/Medium/Low
+
+### Onboarding Flow Design
+- **Activation goal**: What they should achieve
+- **Step-by-step flow**: Each screen/state
+- **Checklist items**: If applicable
+- **Empty states**: Copy and CTA
+- **Email sequence**: Triggers and content
+- **Metrics plan**: What to measure
+
+### Copy Deliverables
+- Welcome screen copy
+- Checklist items with microcopy
+- Empty state copy
+- Tooltip content
+- Email sequence copy
+- Milestone celebration copy
+
+---
+
+## Common Patterns by Product Type
+
+### B2B SaaS Tool
+1. Short setup wizard (use case selection)
+2. First value-generating action
+3. Team invitation prompt
+4. Checklist for deeper setup
+
+### Marketplace/Platform
+1. Complete profile
+2. First search/browse
+3. First transaction
+4. Repeat engagement loop
+
+### Mobile App
+1. Permission requests (strategic timing)
+2. Quick win in first session
+3. Push notification setup
+4. Habit loop establishment
+
+### Content/Social Platform
+1. Follow/customize feed
+2. First content consumption
+3. First content creation
+4. Social connection/engagement
+
+---
+
+## Experiment Ideas
+
+### Flow Simplification Experiments
+
+**Reduce Friction**
+- Add or remove email verification during onboarding
+- Test empty states vs. pre-populated dummy data
+- Provide pre-filled templates to accelerate setup
+- Add OAuth options for faster account linking
+- Reduce number of required onboarding steps
+
+**Step Sequencing**
+- Test different ordering of onboarding steps
+- Lead with highest-value features first
+- Move friction-heavy steps later in flow
+- Test required vs. optional step balance
+
+**Progress & Motivation**
+- Add progress bars or completion percentages
+- Test onboarding checklists (3-5 items vs. 5-7 items)
+- Gamify milestones with badges or rewards
+- Show "X% complete" messaging
+
+---
+
+### Guided Experience Experiments
+
+**Product Tours**
+- Add interactive product tours (Navattic, Storylane)
+- Test tooltip-based guidance vs. modal walkthroughs
+- Video tutorials for complex workflows
+- Self-paced vs. guided tour options
+
+**CTA Optimization**
+- Test CTA text variations during onboarding
+- Test CTA placement within onboarding screens
+- Add in-app tooltips for advanced features
+- Sticky CTAs that persist during onboarding
+
+---
+
+### Personalization Experiments
+
+**User Segmentation**
+- Segment users by role to show relevant features
+- Segment by goal to customize onboarding path
+- Create role-specific dashboards
+- Ask use-case question to personalize flow
+
+**Dynamic Content**
+- Personalized welcome messages
+- Industry-specific examples and templates
+- Dynamic feature recommendations based on answers
+
+---
+
+### Quick Wins & Engagement Experiments
+
+**Time-to-Value**
+- Highlight quick wins early ("Complete your first X")
+- Show success messages after key actions
+- Display progress celebrations at milestones
+- Suggest next steps after each completion
+
+**Support & Help**
+- Offer free onboarding calls for complex products
+- Add contextual help throughout onboarding
+- Test chat support availability during onboarding
+- Proactive outreach for stuck users
+
+---
+
+### Email & Multi-Channel Experiments
+
+**Onboarding Emails**
+- Personalized welcome email from founder
+- Behavior-based emails (triggered by actions/inactions)
+- Test email timing and frequency
+- Include quick tips and video content
+
+**Feedback Loops**
+- Add NPS survey during onboarding
+- Ask "What's blocking you?" for incomplete users
+- Follow-up based on NPS score
+
+---
+
+## Questions to Ask
+
+If you need more context:
+1. What action most correlates with retention?
+2. What happens immediately after signup?
+3. Where do users currently drop off?
+4. What's your activation rate target?
+5. Do you have cohort analysis on successful vs. churned users?
+
+---
+
+## Related Skills
+
+- **signup-flow-cro**: For optimizing the signup before onboarding
+- **email-sequence**: For onboarding email series
+- **paywall-upgrade-cro**: For converting to paid during/after onboarding
+- **ab-test-setup**: For testing onboarding changes

package/skills/one-drive-automation/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: one-drive-automation
+description: "Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# OneDrive Automation via Rube MCP
+
+Automate OneDrive operations including file upload/download, search, folder management, sharing links, permissions management, and drive browsing through Composio's OneDrive toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active OneDrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`
+- 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.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`
+3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search and Browse Files
+
+**When to use**: User wants to find files or browse folder contents in OneDrive
+
+**Tool sequence**:
+1. `ONE_DRIVE_GET_DRIVE` - Verify drive access and get drive details [Prerequisite]
+2. `ONE_DRIVE_SEARCH_ITEMS` - Keyword search across filenames, metadata, and content [Required]
+3. `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` - List all items in the root of a drive [Optional]
+4. `ONE_DRIVE_GET_ITEM` - Get detailed metadata for a specific item, expand children [Optional]
+5. `ONE_DRIVE_ONEDRIVE_FIND_FILE` - Find a specific file by exact name in a folder [Optional]
+6. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Find a specific folder by name [Optional]
+7. `ONE_DRIVE_LIST_DRIVES` - List all accessible drives [Optional]
+
+**Key parameters**:
+- `q`: Search query (plain keywords only, NOT KQL syntax)
+- `search_scope`: `"root"` (folder hierarchy) or `"drive"` (includes shared items)
+- `top`: Max items per page (default 200)
+- `skip_token`: Pagination token from `@odata.nextLink`
+- `select`: Comma-separated fields to return (e.g., `"id,name,webUrl,size"`)
+- `orderby`: Sort order (e.g., `"name asc"`, `"name desc"`)
+- `item_id`: Item ID for `GET_ITEM`
+- `expand_relations`: Array like `["children"]` or `["thumbnails"]` for `GET_ITEM`
+- `user_id`: `"me"` (default) or specific user ID/email
+
+**Pitfalls**:
+- `ONE_DRIVE_SEARCH_ITEMS` does NOT support KQL operators (`folder:`, `file:`, `filetype:`, `path:`); these are treated as literal text
+- Wildcard characters (`*`, `?`) are NOT supported and are auto-removed; use file extension keywords instead (e.g., `"pdf"` not `"*.pdf"`)
+- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` returns only root-level contents; use recursive `ONE_DRIVE_GET_ITEM` with `expand_relations: ["children"]` for deeper levels
+- Large folders paginate; always follow `skip_token` / `@odata.nextLink` until exhausted
+- Some drive ID formats may return "ObjectHandle is Invalid" errors due to Microsoft Graph API limitations
+
+### 2. Upload and Download Files
+
+**When to use**: User wants to upload files to OneDrive or download files from it
+
+**Tool sequence**:
+1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the target folder [Prerequisite]
+2. `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` - Upload a file to a specified folder [Required for upload]
+3. `ONE_DRIVE_DOWNLOAD_FILE` - Download a file by item ID [Required for download]
+4. `ONE_DRIVE_GET_ITEM` - Get file details before download [Optional]
+
+**Key parameters**:
+- `file`: FileUploadable object with `s3key`, `mimetype`, and `name` for uploads
+- `folder`: Destination path (e.g., `"/Documents/Reports"`) or folder ID for uploads
+- `item_id`: File's unique identifier for downloads
+- `file_name`: Desired filename with extension for downloads
+- `drive_id`: Specific drive ID (for SharePoint or OneDrive for Business)
+- `user_id`: `"me"` (default) or specific user identifier
+
+**Pitfalls**:
+- Upload automatically renames on conflict (no overwrite option by default)
+- Large files are automatically handled via chunking
+- `drive_id` overrides `user_id` when both are provided
+- Item IDs vary by platform: OneDrive for Business uses `01...` prefix, OneDrive Personal uses `HASH!NUMBER` format
+- Item IDs are case-sensitive; use exactly as returned from API
+
+### 3. Share Files and Manage Permissions
+
+**When to use**: User wants to share files/folders or manage who has access
+
+**Tool sequence**:
+1. `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the item [Prerequisite]
+2. `ONE_DRIVE_GET_ITEM_PERMISSIONS` - Check current permissions [Prerequisite]
+3. `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` - Grant access to specific users [Required]
+4. `ONE_DRIVE_CREATE_LINK` - Create a shareable link [Optional]
+5. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Update item metadata [Optional]
+
+**Key parameters**:
+- `item_id`: The file or folder to share
+- `recipients`: Array of objects with `email` or `object_id`
+- `roles`: Array with `"read"` or `"write"`
+- `send_invitation`: `true` to send notification email, `false` for silent permission grant
+- `require_sign_in`: `true` to require authentication to access
+- `message`: Custom message for invitation (max 2000 characters)
+- `expiration_date_time`: ISO 8601 date for permission expiry
+- `retain_inherited_permissions`: `true` (default) to keep existing inherited permissions
+
+**Pitfalls**:
+- Using wrong `item_id` with `INVITE_USER_TO_DRIVE_ITEM` changes permissions on unintended items; always verify first
+- Write or higher roles are impactful; get explicit user confirmation before granting
+- `GET_ITEM_PERMISSIONS` returns inherited and owner entries; do not assume response only reflects recent changes
+- `permissions` cannot be expanded via `ONE_DRIVE_GET_ITEM`; use the separate permissions endpoint
+- At least one of `require_sign_in` or `send_invitation` must be `true`
+
+### 4. Manage Folders (Create, Move, Delete, Copy)
+
+**When to use**: User wants to create, move, rename, delete, or copy files and folders
+
+**Tool sequence**:
+1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate source and destination folders [Prerequisite]
+2. `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` - Create a new folder [Required for create]
+3. `ONE_DRIVE_MOVE_ITEM` - Move a file or folder to a new location [Required for move]
+4. `ONE_DRIVE_COPY_ITEM` - Copy a file or folder (async operation) [Required for copy]
+5. `ONE_DRIVE_DELETE_ITEM` - Move item to recycle bin [Required for delete]
+6. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Rename or update item properties [Optional]
+
+**Key parameters**:
+- `name`: Folder name for creation or new name for rename/copy
+- `parent_folder`: Path (e.g., `"/Documents/Reports"`) or folder ID for creation
+- `itemId`: Item to move
+- `parentReference`: Object with `id` (destination folder ID) for moves: `{"id": "folder_id"}`
+- `item_id`: Item to copy or delete
+- `parent_reference`: Object with `id` and optional `driveId` for copy destination
+- `@microsoft.graph.conflictBehavior`: `"fail"`, `"replace"`, or `"rename"` for copies
+- `if_match`: ETag for optimistic concurrency on deletes
+
+**Pitfalls**:
+- `ONE_DRIVE_MOVE_ITEM` does NOT support cross-drive moves; use `ONE_DRIVE_COPY_ITEM` for cross-drive transfers
+- `parentReference` for moves requires folder ID (not folder name); resolve with `ONEDRIVE_FIND_FOLDER` first
+- `ONE_DRIVE_COPY_ITEM` is asynchronous; response provides a URL to monitor progress
+- `ONE_DRIVE_DELETE_ITEM` moves to recycle bin, not permanent deletion
+- Folder creation auto-renames on conflict (e.g., "New Folder" becomes "New Folder 1")
+- Provide either `name` or `parent_reference` (or both) for `ONE_DRIVE_COPY_ITEM`
+
+### 5. Track Changes and Drive Information
+
+**When to use**: User wants to monitor changes or get drive/quota information
+
+**Tool sequence**:
+1. `ONE_DRIVE_GET_DRIVE` - Get drive properties and metadata [Required]
+2. `ONE_DRIVE_GET_QUOTA` - Check storage quota (total, used, remaining) [Optional]
+3. `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` - Track changes in SharePoint site drives [Optional]
+4. `ONE_DRIVE_GET_ITEM_VERSIONS` - Get version history of a file [Optional]
+
+**Key parameters**:
+- `drive_id`: Drive identifier (or `"me"` for personal drive)
+- `site_id`: SharePoint site identifier for delta tracking
+- `token`: Delta token (`"latest"` for current state, URL for next page, or timestamp)
+- `item_id`: File ID for version history
+
+**Pitfalls**:
+- Delta queries are only available for SharePoint site drives via `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA`
+- Token `"latest"` returns current delta token without items (useful as starting point)
+- Deep or large drives can take several minutes to crawl; use batching and resume logic
+
+## Common Patterns
+
+### ID Resolution
+- **User**: Use `"me"` for authenticated user or specific user email/GUID
+- **Item ID from find**: Use `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` to get item IDs
+- **Item ID from search**: Extract from `ONE_DRIVE_SEARCH_ITEMS` results
+- **Drive ID**: Use `ONE_DRIVE_LIST_DRIVES` or `ONE_DRIVE_GET_DRIVE` to discover drives
+- **Folder path to ID**: Use `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` with path, then extract ID from response
+
+ID formats vary by platform:
+- OneDrive for Business/SharePoint: `01NKDM7HMOJTVYMDOSXFDK2QJDXCDI3WUK`
+- OneDrive Personal: `D4648F06C91D9D3D!54927`
+
+### Pagination
+OneDrive uses token-based pagination:
+- Follow `@odata.nextLink` or `skip_token` until no more pages
+- Set `top` for page size (varies by endpoint)
+- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` auto-handles pagination internally
+- Aggressive parallel requests can trigger HTTP 429; honor `Retry-After` headers
+
+### Path vs ID
+Most OneDrive tools accept either paths or IDs:
+- **Paths**: Start with `/` (e.g., `"/Documents/Reports"`)
+- **IDs**: Use unique item identifiers from API responses
+- **Item paths for permissions**: Use `:/path/to/item:/` format
+
+## Known Pitfalls
+
+### ID Formats
+- Item IDs are case-sensitive and platform-specific
+- Never use web URLs, sharing links, or manually constructed identifiers as item IDs
+- Always use IDs exactly as returned from Microsoft Graph API
+
+### Rate Limits
+- Aggressive parallel `ONE_DRIVE_GET_ITEM` calls can trigger HTTP 429 Too Many Requests
+- Honor `Retry-After` headers and implement throttling
+- Deep drive crawls should use batching with delays
+
+### Search Limitations
+- No KQL support; use plain keywords only
+- No wildcard characters; use extension keywords (e.g., `"pdf"` not `"*.pdf"`)
+- No path-based filtering in search; use folder listing instead
+- `q='*'` wildcard-only queries return HTTP 400 invalidRequest
+
+### Parameter Quirks
+- `drive_id` overrides `user_id` when both are provided
+- `permissions` cannot be expanded via `GET_ITEM`; use dedicated permissions endpoint
+- Move operations require folder IDs in `parentReference`, not folder names
+- Copy operations are asynchronous; response provides monitoring URL
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search files | `ONE_DRIVE_SEARCH_ITEMS` | `q`, `search_scope`, `top` |
+| List root items | `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` | `user_id`, `select`, `top` |
+| Get item details | `ONE_DRIVE_GET_ITEM` | `item_id`, `expand_relations` |
+| Find file by name | `ONE_DRIVE_ONEDRIVE_FIND_FILE` | `name`, `folder` |
+| Find folder by name | `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` | `name`, `folder` |
+| Upload file | `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` | `file`, `folder` |
+| Download file | `ONE_DRIVE_DOWNLOAD_FILE` | `item_id`, `file_name` |
+| Create folder | `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` | `name`, `parent_folder` |
+| Move item | `ONE_DRIVE_MOVE_ITEM` | `itemId`, `parentReference` |
+| Copy item | `ONE_DRIVE_COPY_ITEM` | `item_id`, `parent_reference`, `name` |
+| Delete item | `ONE_DRIVE_DELETE_ITEM` | `item_id` |
+| Share with users | `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` | `item_id`, `recipients`, `roles` |
+| Create share link | `ONE_DRIVE_CREATE_LINK` | `item_id`, link type |
+| Get permissions | `ONE_DRIVE_GET_ITEM_PERMISSIONS` | `item_id` |
+| Update metadata | `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` | `item_id`, fields |
+| Get drive info | `ONE_DRIVE_GET_DRIVE` | `drive_id` |
+| List drives | `ONE_DRIVE_LIST_DRIVES` | user/group/site scope |
+| Get quota | `ONE_DRIVE_GET_QUOTA` | (none) |
+| Track changes | `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` | `site_id`, `token` |
+| Version history | `ONE_DRIVE_GET_ITEM_VERSIONS` | `item_id` |

package/skills/openapi-spec-generation/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: openapi-spec-generation
+description: Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
+---
+
+# OpenAPI Spec Generation
+
+Comprehensive patterns for creating, maintaining, and validating OpenAPI 3.1 specifications for RESTful APIs.
+
+## Use this skill when
+
+- Creating API documentation from scratch
+- Generating OpenAPI specs from existing code
+- Designing API contracts (design-first approach)
+- Validating API implementations against specs
+- Generating client SDKs from specs
+- Setting up API documentation portals
+
+## Do not use this skill when
+
+- The task is unrelated to openapi spec generation
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.