skill-library-mcp 1.0.0

package/skills/oss-hunter/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: oss-hunter
+description: Automatically hunt for high-impact OSS contribution opportunities in trending repositories.
+risk: safe
+source: https://github.com/jackjin1997/ClawForge
+metadata: {"openclaw":{"emoji":"🎯","category":"developer"}}
+---
+
+# OSS Hunter 🎯
+
+A precision skill for agents to find, analyze, and strategize for high-impact Open Source contributions. This skill helps you become a top-tier contributor by identifying the most "mergeable" and influential issues in trending repositories.
+
+## When to Use
+
+- Use when the user asks to find open source issues to work on.
+- Use when searching for "help wanted" or "good first issue" tasks in specific domains like AI or Web3.
+- Use to generate a "Contribution Dossier" with ready-to-execute strategies for trending projects.
+
+## Quick Start
+
+Ask your agent:
+- "Find me some help-wanted issues in trending AI repositories."
+- "Hunt for bug fixes in langchain-ai/langchain that are suitable for a quick PR."
+- "Generate a contribution dossier for the most recent trending projects on GitHub."
+
+## Workflow
+
+When hunting for contributions, the agent follows this multi-stage protocol:
+
+### Phase 1: Repository Discovery
+Use `web_search` or `gh api` to find trending repositories.
+Focus on:
+- Stars > 1000
+- Recent activity (pushed within 24 hours)
+- Relevant topics (AI, Agentic, Web3, Tooling)
+
+### Phase 2: Issue Extraction
+Search for specific labels:
+- `help-wanted`
+- `good-first-issue`
+- `bug`
+- `v1` / `roadmap`
+
+```bash
+gh issue list --repo owner/repo --label "help wanted" --limit 10
+```
+
+### Phase 3: Feasibility Analysis
+Analyze the issue:
+1. **Reproducibility**: Is there a code snippet to reproduce the bug?
+2. **Impact**: How many users does this affect?
+3. **Mergeability**: Check recent PR history. Does the maintainer merge community PRs quickly?
+4. **Complexity**: Can this be solved by an agent with the current tools?
+
+### Phase 4: The Dossier
+Generate a structured report for the human:
+- **Project Name & Stars**
+- **Issue Link & Description**
+- **Root Cause Analysis** (based on code inspection)
+- **Proposed Fix Strategy**
+- **Confidence Score** (1-10)
+
+## Limitations
+
+- Accuracy depends on the availability of `gh` CLI or `web_search` tools.
+- Analysis is limited by context window when reading very large repositories.
+- Cannot guarantee PR acceptance (maintainer discretion).
+
+---
+
+## Contributing to the Matrix
+
+Build a better hunter by adding new heuristics to Phase 3. Submit your improvements to the [ClawForge](https://github.com/jackjin1997/ClawForge).
+
+*Powered by OpenClaw & ClawForge.*

package/skills/outlook-automation/SKILL.md

@@ -0,0 +1,191 @@
+---
+name: outlook-automation
+description: "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Outlook Automation via Rube MCP
+
+Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Outlook connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`
+- 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 `outlook`
+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 Filter Emails
+
+**When to use**: User wants to find specific emails across their mailbox
+
+**Tool sequence**:
+1. `OUTLOOK_SEARCH_MESSAGES` - Search with KQL syntax across all folders [Required]
+2. `OUTLOOK_GET_MESSAGE` - Get full message details [Optional]
+3. `OUTLOOK_LIST_OUTLOOK_ATTACHMENTS` - List message attachments [Optional]
+4. `OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT` - Download attachment [Optional]
+
+**Key parameters**:
+- `query`: KQL search string (from:, to:, subject:, received:, hasattachment:)
+- `from_index`: Pagination start (0-based)
+- `size`: Results per page (max 25)
+- `message_id`: Message ID (use hitId from search results)
+
+**Pitfalls**:
+- Only works with Microsoft 365/Enterprise accounts (not @hotmail.com/@outlook.com)
+- Pagination relies on hitsContainers[0].moreResultsAvailable; stop only when false
+- Use hitId from search results as message_id for downstream calls, not resource.id
+- Index latency: very recent emails may not appear immediately
+- Inline images appear as attachments; filter by mimetype for real documents
+
+### 2. Query Emails in a Folder
+
+**When to use**: User wants to list emails in a specific folder with OData filters
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_MAIL_FOLDERS` - List mail folders to get folder IDs [Prerequisite]
+2. `OUTLOOK_QUERY_EMAILS` - Query emails with structured filters [Required]
+
+**Key parameters**:
+- `folder`: Folder name ('inbox', 'sentitems', 'drafts') or folder ID
+- `filter`: OData filter (e.g., `isRead eq false and importance eq 'high'`)
+- `top`: Max results (1-1000)
+- `orderby`: Sort field and direction
+- `select`: Array of fields to return
+
+**Pitfalls**:
+- QUERY_EMAILS searches a SINGLE folder only; use SEARCH_MESSAGES for cross-folder search
+- Custom folders require folder IDs, not display names; use LIST_MAIL_FOLDERS
+- Always check response['@odata.nextLink'] for pagination
+- Cannot filter by recipient or body content; use SEARCH_MESSAGES for that
+
+### 3. Manage Calendar Events
+
+**When to use**: User wants to list, search, or inspect calendar events
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_EVENTS` - List events with filters [Optional]
+2. `OUTLOOK_GET_CALENDAR_VIEW` - Get events in a time window [Optional]
+3. `OUTLOOK_GET_EVENT` - Get specific event details [Optional]
+4. `OUTLOOK_LIST_CALENDARS` - List available calendars [Optional]
+5. `OUTLOOK_GET_SCHEDULE` - Get free/busy info [Optional]
+
+**Key parameters**:
+- `filter`: OData filter (use start/dateTime, NOT receivedDateTime)
+- `start_datetime`/`end_datetime`: ISO 8601 for calendar view
+- `timezone`: IANA timezone (e.g., 'America/New_York')
+- `calendar_id`: Optional non-primary calendar ID
+- `select`: Fields to return
+
+**Pitfalls**:
+- Use calendar event properties only (start/dateTime, end/dateTime), NOT email properties (receivedDateTime)
+- Calendar view requires start_datetime and end_datetime
+- Recurring events need `expand_recurring_events=true` to see individual occurrences
+- Decline status is per-attendee via attendees[].status.response
+
+### 4. Manage Contacts
+
+**When to use**: User wants to list, create, or organize contacts
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_CONTACTS` - List contacts [Optional]
+2. `OUTLOOK_CREATE_CONTACT` - Create a new contact [Optional]
+3. `OUTLOOK_GET_CONTACT_FOLDERS` - List contact folders [Optional]
+4. `OUTLOOK_CREATE_CONTACT_FOLDER` - Create contact folder [Optional]
+
+**Key parameters**:
+- `givenName`/`surname`: Contact name
+- `emailAddresses`: Array of email objects
+- `displayName`: Full display name
+- `contact_folder_id`: Optional folder for contacts
+
+**Pitfalls**:
+- Contact creation supports many fields but only givenName or surname is needed
+
+### 5. Manage Mail Folders
+
+**When to use**: User wants to organize mail folders
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_MAIL_FOLDERS` - List top-level folders [Required]
+2. `OUTLOOK_LIST_CHILD_MAIL_FOLDERS` - List subfolders [Optional]
+3. `OUTLOOK_CREATE_MAIL_FOLDER` - Create a new folder [Optional]
+
+**Key parameters**:
+- `parent_folder_id`: Well-known name or folder ID
+- `displayName`: New folder name
+- `include_hidden_folders`: Show hidden folders
+
+**Pitfalls**:
+- Well-known folder names: 'inbox', 'sentitems', 'drafts', 'deleteditems', 'junkemail', 'archive'
+- Custom folder operations require the folder ID, not display name
+
+## Common Patterns
+
+### KQL Search Syntax
+
+**Property filters**:
+- `from:user@example.com` - From sender
+- `to:recipient@example.com` - To recipient
+- `subject:invoice` - Subject contains
+- `received>=2025-01-01` - Date filter
+- `hasattachment:yes` - Has attachments
+
+**Combinators**:
+- `AND` - Both conditions
+- `OR` - Either condition
+- Parentheses for grouping
+
+### OData Filter Syntax
+
+**Email filters**:
+- `isRead eq false` - Unread emails
+- `importance eq 'high'` - High importance
+- `hasAttachments eq true` - Has attachments
+- `receivedDateTime ge 2025-01-01T00:00:00Z` - Date filter
+
+**Calendar filters**:
+- `start/dateTime ge '2025-01-01T00:00:00Z'` - Events after date
+- `contains(subject, 'Meeting')` - Subject contains text
+
+## Known Pitfalls
+
+**Account Types**:
+- SEARCH_MESSAGES requires Microsoft 365/Enterprise accounts
+- Personal accounts (@hotmail.com, @outlook.com) have limited API access
+
+**Field Confusion**:
+- Email properties (receivedDateTime) differ from calendar properties (start/dateTime)
+- Do NOT use email fields in calendar queries or vice versa
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search emails | OUTLOOK_SEARCH_MESSAGES | query, from_index, size |
+| Query folder | OUTLOOK_QUERY_EMAILS | folder, filter, top |
+| Get message | OUTLOOK_GET_MESSAGE | message_id |
+| List attachments | OUTLOOK_LIST_OUTLOOK_ATTACHMENTS | message_id |
+| Download attachment | OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT | message_id, attachment_id |
+| List folders | OUTLOOK_LIST_MAIL_FOLDERS | (none) |
+| Child folders | OUTLOOK_LIST_CHILD_MAIL_FOLDERS | parent_folder_id |
+| List events | OUTLOOK_LIST_EVENTS | filter, timezone |
+| Calendar view | OUTLOOK_GET_CALENDAR_VIEW | start_datetime, end_datetime |
+| Get event | OUTLOOK_GET_EVENT | event_id |
+| List calendars | OUTLOOK_LIST_CALENDARS | (none) |
+| Free/busy | OUTLOOK_GET_SCHEDULE | schedules, times |
+| List contacts | OUTLOOK_LIST_CONTACTS | top, filter |
+| Create contact | OUTLOOK_CREATE_CONTACT | givenName, emailAddresses |
+| Contact folders | OUTLOOK_GET_CONTACT_FOLDERS | (none) |

package/skills/outlook-calendar-automation/SKILL.md

@@ -0,0 +1,236 @@
+---
+name: outlook-calendar-automation
+description: "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Outlook Calendar Automation via Rube MCP
+
+Automate Outlook Calendar operations through Composio's Outlook toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Outlook connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`
+- 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 `outlook`
+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. Create Calendar Events
+
+**When to use**: User wants to schedule a new event on their Outlook calendar
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_CALENDARS` - List available calendars [Optional]
+2. `OUTLOOK_CALENDAR_CREATE_EVENT` - Create the event [Required]
+
+**Key parameters**:
+- `subject`: Event title
+- `start_datetime`: ISO 8601 start time (e.g., '2025-01-03T10:00:00')
+- `end_datetime`: ISO 8601 end time (must be after start)
+- `time_zone`: IANA or Windows timezone (e.g., 'America/New_York', 'Pacific Standard Time')
+- `attendees_info`: Array of email strings or attendee objects
+- `body`: Event description (plain text or HTML)
+- `is_html`: Set true if body contains HTML
+- `location`: Physical location string
+- `is_online_meeting`: Set true for Teams meeting link
+- `online_meeting_provider`: 'teamsForBusiness' for Teams integration
+- `show_as`: 'free', 'tentative', 'busy', 'oof'
+
+**Pitfalls**:
+- start_datetime must be chronologically before end_datetime
+- time_zone is required and must be a valid IANA or Windows timezone name
+- Adding attendees can trigger invitation emails immediately
+- To generate a Teams meeting link, set BOTH is_online_meeting=true AND online_meeting_provider='teamsForBusiness'
+- user_id defaults to 'me'; use email or UUID for other users' calendars
+
+### 2. List and Search Events
+
+**When to use**: User wants to find events on their calendar
+
+**Tool sequence**:
+1. `OUTLOOK_GET_MAILBOX_SETTINGS` - Get user timezone for accurate queries [Prerequisite]
+2. `OUTLOOK_LIST_EVENTS` - Search events with filters [Required]
+3. `OUTLOOK_GET_EVENT` - Get full details for a specific event [Optional]
+4. `OUTLOOK_GET_CALENDAR_VIEW` - Get events active during a time window [Alternative]
+
+**Key parameters**:
+- `filter`: OData filter string (e.g., "start/dateTime ge '2024-07-01T00:00:00Z'")
+- `select`: Array of properties to return
+- `orderby`: Sort criteria (e.g., ['start/dateTime desc'])
+- `top`: Results per page (1-999)
+- `timezone`: Display timezone for results
+- `start_datetime`/`end_datetime`: For CALENDAR_VIEW time window (UTC with Z suffix)
+
+**Pitfalls**:
+- OData filter datetime values require single quotes and Z suffix
+- Use 'start/dateTime' for event start filtering, NOT 'receivedDateTime' (that is for emails)
+- 'createdDateTime' supports orderby/select but NOT filtering
+- Pagination: follow @odata.nextLink until all pages are collected
+- CALENDAR_VIEW is better for "what's on my calendar today" queries (includes spanning events)
+- LIST_EVENTS is better for keyword/category filtering
+- Response events have start/end nested as start.dateTime and end.dateTime
+
+### 3. Update Events
+
+**When to use**: User wants to modify an existing calendar event
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_EVENTS` - Find the event to update [Prerequisite]
+2. `OUTLOOK_UPDATE_CALENDAR_EVENT` - Update the event [Required]
+
+**Key parameters**:
+- `event_id`: Unique event identifier (from LIST_EVENTS)
+- `subject`: New event title (optional)
+- `start_datetime`/`end_datetime`: New times (optional)
+- `time_zone`: Timezone for new times
+- `attendees`: Updated attendee list (replaces existing if provided)
+- `body`: Updated description with contentType and content
+- `location`: Updated location
+
+**Pitfalls**:
+- UPDATE merges provided fields with existing event; unspecified fields are preserved
+- Providing attendees replaces the ENTIRE attendee list; include all desired attendees
+- Providing categories replaces the ENTIRE category list
+- Updating times may trigger re-sends to attendees
+- event_id is required; obtain from LIST_EVENTS first
+
+### 4. Delete Events and Decline Invitations
+
+**When to use**: User wants to remove an event or decline a meeting invitation
+
+**Tool sequence**:
+1. `OUTLOOK_DELETE_EVENT` - Delete an event [Optional]
+2. `OUTLOOK_DECLINE_EVENT` - Decline a meeting invitation [Optional]
+
+**Key parameters**:
+- `event_id`: Event to delete or decline
+- `send_notifications`: Send cancellation notices to attendees (default true)
+- `comment`: Reason for declining (for DECLINE_EVENT)
+- `proposedNewTime`: Suggest alternative time when declining
+
+**Pitfalls**:
+- Deletion with send_notifications=true sends cancellation emails
+- Declining supports proposing a new time with start/end in ISO 8601 format
+- Deleting a recurring event master deletes all occurrences
+- sendResponse in DECLINE_EVENT controls whether the organizer is notified
+
+### 5. Find Available Meeting Times
+
+**When to use**: User wants to find optimal meeting slots across multiple people
+
+**Tool sequence**:
+1. `OUTLOOK_FIND_MEETING_TIMES` - Get meeting time suggestions [Required]
+2. `OUTLOOK_GET_SCHEDULE` - Check free/busy for specific people [Alternative]
+
+**Key parameters**:
+- `attendees`: Array of attendee objects with email and type
+- `meetingDuration`: ISO 8601 duration (e.g., 'PT1H' for 1 hour, 'PT30M' for 30 min)
+- `timeConstraint`: Time slots to search within
+- `minimumAttendeePercentage`: Minimum confidence threshold (0-100)
+- `Schedules`: Email array for GET_SCHEDULE
+- `StartTime`/`EndTime`: Time window for schedule lookup (max 62 days)
+
+**Pitfalls**:
+- FIND_MEETING_TIMES searches within work hours by default; use activityDomain='unrestricted' for 24/7
+- Time constraint time slots require dateTime and timeZone for both start and end
+- GET_SCHEDULE period cannot exceed 62 days
+- Meeting suggestions respect attendee availability but may return suboptimal times for complex groups
+
+## Common Patterns
+
+### Event ID Resolution
+
+```
+1. Call OUTLOOK_LIST_EVENTS with time-bound filter
+2. Find target event by subject or other criteria
+3. Extract event id (e.g., 'AAMkAGI2TAAA=')
+4. Use in UPDATE, DELETE, or GET_EVENT calls
+```
+
+### OData Filter Syntax for Calendar
+
+**Time range filter**:
+```
+filter: "start/dateTime ge '2024-07-01T00:00:00Z' and start/dateTime le '2024-07-31T23:59:59Z'"
+```
+
+**Subject contains**:
+```
+filter: "contains(subject, 'Project Review')"
+```
+
+**Combined**:
+```
+filter: "contains(subject, 'Review') and categories/any(c:c eq 'Work')"
+```
+
+### Timezone Handling
+
+- Get user timezone: `OUTLOOK_GET_MAILBOX_SETTINGS` with select=['timeZone']
+- Use consistent timezone in filter datetime values
+- Calendar View requires UTC timestamps with Z suffix
+- LIST_EVENTS filter accepts timezone in datetime values
+
+### Online Meeting Creation
+
+```
+1. Set is_online_meeting: true
+2. Set online_meeting_provider: 'teamsForBusiness'
+3. Create event with OUTLOOK_CALENDAR_CREATE_EVENT
+4. Teams join link available in response onlineMeeting field
+5. Or retrieve via OUTLOOK_GET_EVENT for the full join URL
+```
+
+## Known Pitfalls
+
+**DateTime Formats**:
+- ISO 8601 format required: '2025-01-03T10:00:00'
+- Calendar View requires UTC with Z: '2025-01-03T10:00:00Z'
+- Filter values need single quotes: "'2025-01-03T00:00:00Z'"
+- Timezone mismatches shift event boundaries; always resolve user timezone first
+
+**OData Filter Errors**:
+- 400 Bad Request usually indicates filter syntax issues
+- Not all event properties support filtering (createdDateTime does not)
+- Retry with adjusted syntax/bounds on 400 errors
+- Valid filter fields: start/dateTime, end/dateTime, subject, categories, isAllDay
+
+**Attendee Management**:
+- Adding attendees triggers invitation emails
+- Updating attendees replaces the full list; include all desired attendees
+- Attendee types: 'required', 'optional', 'resource'
+- Calendar delegation affects which calendars are accessible
+
+**Response Structure**:
+- Events nested at response.data.value
+- Event times at event.start.dateTime and event.end.dateTime
+- Calendar View may nest at data.results[i].response.data.value
+- Parse defensively with fallbacks for different nesting levels
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create event | OUTLOOK_CALENDAR_CREATE_EVENT | subject, start_datetime, end_datetime, time_zone |
+| List events | OUTLOOK_LIST_EVENTS | filter, select, top, timezone |
+| Get event details | OUTLOOK_GET_EVENT | event_id |
+| Calendar view | OUTLOOK_GET_CALENDAR_VIEW | start_datetime, end_datetime |
+| Update event | OUTLOOK_UPDATE_CALENDAR_EVENT | event_id, subject, start_datetime |
+| Delete event | OUTLOOK_DELETE_EVENT | event_id, send_notifications |
+| Decline event | OUTLOOK_DECLINE_EVENT | event_id, comment |
+| Find meeting times | OUTLOOK_FIND_MEETING_TIMES | attendees, meetingDuration |
+| Get schedule | OUTLOOK_GET_SCHEDULE | Schedules, StartTime, EndTime |
+| List calendars | OUTLOOK_LIST_CALENDARS | user_id |
+| Mailbox settings | OUTLOOK_GET_MAILBOX_SETTINGS | select |