skill-library-mcp 1.0.0

package/skills/skill-rails-upgrade/SKILL.md

@@ -0,0 +1,408 @@
+---
+name: skill-rails-upgrade
+description: "Analyze Rails apps and provide upgrade assessments"
+source: "https://github.com/robzolkos/skill-rails-upgrade"
+risk: safe
+---
+
+## When to Use This Skill
+
+Analyze Rails apps and provide upgrade assessments
+
+Use this skill when working with analyze rails apps and provide upgrade assessments.
+# Rails Upgrade Analyzer
+
+Analyze the current Rails application and provide a comprehensive upgrade assessment with selective file merging.
+
+## Step 1: Verify Rails Application
+
+Check that we're in a Rails application by looking for these files:
+- `Gemfile` (must exist and contain 'rails')
+- `config/application.rb` (Rails application config)
+- `config/environment.rb` (Rails environment)
+
+If any of these are missing or don't indicate a Rails app, stop and inform the user this doesn't appear to be a Rails application.
+
+## Step 2: Get Current Rails Version
+
+Extract the current Rails version from:
+1. First, check `Gemfile.lock` for the exact installed version (look for `rails (x.y.z)`)
+2. If not found, check `Gemfile` for the version constraint
+
+Report the exact current version (e.g., `7.1.3`).
+
+## Step 3: Find Latest Rails Version
+
+Use the GitHub CLI to fetch the latest Rails release:
+
+```bash
+gh api repos/rails/rails/releases/latest --jq '.tag_name'
+```
+
+This returns the latest stable version tag (e.g., `v8.0.1`). Strip the 'v' prefix for comparison.
+
+Also check recent tags to understand the release landscape:
+
+```bash
+gh api repos/rails/rails/tags --jq '.[0:10] | .[].name'
+```
+
+## Step 4: Determine Upgrade Type
+
+Compare current and latest versions to classify the upgrade:
+
+- **Patch upgrade**: Same major.minor, different patch (e.g., 7.1.3 → 7.1.5)
+- **Minor upgrade**: Same major, different minor (e.g., 7.1.3 → 7.2.0)
+- **Major upgrade**: Different major version (e.g., 7.1.3 → 8.0.0)
+
+## Step 5: Fetch Upgrade Guide
+
+Use WebFetch to get the official Rails upgrade guide:
+
+URL: `https://guides.rubyonrails.org/upgrading_ruby_on_rails.html`
+
+Look for sections relevant to the version jump. The guide is organized by target version with sections like:
+- "Upgrading from Rails X.Y to Rails X.Z"
+- Breaking changes
+- Deprecation warnings
+- Configuration changes
+- Required migrations
+
+Extract and summarize the relevant sections for the user's specific upgrade path.
+
+## Step 6: Fetch Rails Diff
+
+Use WebFetch to get the diff between versions from railsdiff.org:
+
+URL: `https://railsdiff.org/{current_version}/{target_version}`
+
+For example: `https://railsdiff.org/7.1.3/8.0.0`
+
+This shows:
+- Changes to default configuration files
+- New files that need to be added
+- Modified initializers
+- Updated dependencies
+- Changes to bin/ scripts
+
+Summarize the key file changes.
+
+## Step 7: Check JavaScript Dependencies
+
+Rails applications often include JavaScript packages that should be updated alongside Rails. Check for and report on these dependencies.
+
+### 7.1: Identify JS Package Manager
+
+Check which package manager the app uses:
+
+```bash
+# Check for package.json (npm/yarn)
+ls package.json 2>/dev/null
+
+# Check for importmap (Rails 7+)
+ls config/importmap.rb 2>/dev/null
+```
+
+### 7.2: Check Rails-Related JS Packages
+
+If `package.json` exists, check for these Rails-related packages:
+
+```bash
+# Extract current versions of Rails-related packages
+cat package.json | grep -E '"@hotwired/|"@rails/|"stimulus"|"turbo-rails"' || echo "No Rails JS packages found"
+```
+
+**Key packages to check:**
+
+| Package | Purpose | Version Alignment |
+|---------|---------|-------------------|
+| `@hotwired/turbo-rails` | Turbo Drive/Frames/Streams | Should match Rails version era |
+| `@hotwired/stimulus` | Stimulus JS framework | Generally stable across Rails versions |
+| `@rails/actioncable` | WebSocket support | Should match Rails version |
+| `@rails/activestorage` | Direct uploads | Should match Rails version |
+| `@rails/actiontext` | Rich text editing | Should match Rails version |
+| `@rails/request.js` | Rails UJS replacement | Should match Rails version era |
+
+### 7.3: Check for Updates
+
+For npm/yarn projects, check for available updates:
+
+```bash
+# Using npm
+npm outdated @hotwired/turbo-rails @hotwired/stimulus @rails/actioncable @rails/activestorage 2>/dev/null
+
+# Or check latest versions directly
+npm view @hotwired/turbo-rails version 2>/dev/null
+npm view @rails/actioncable version 2>/dev/null
+```
+
+### 7.4: Check Importmap Pins (if applicable)
+
+If the app uses importmap-rails, check `config/importmap.rb` for pinned versions:
+
+```bash
+cat config/importmap.rb | grep -E 'pin.*turbo|pin.*stimulus|pin.*@rails' || echo "No importmap pins found"
+```
+
+To update importmap pins:
+```bash
+bin/importmap pin @hotwired/turbo-rails
+bin/importmap pin @hotwired/stimulus
+```
+
+### 7.5: JS Dependency Summary
+
+Include in the upgrade summary:
+
+```
+### JavaScript Dependencies
+
+**Package Manager**: [npm/yarn/importmap/none]
+
+| Package | Current | Latest | Action |
+|---------|---------|--------|--------|
+| @hotwired/turbo-rails | 8.0.4 | 8.0.12 | Update recommended |
+| @rails/actioncable | 7.1.0 | 8.0.0 | Update with Rails |
+| ... | ... | ... | ... |
+
+**Recommended JS Updates:**
+- Run `npm update @hotwired/turbo-rails` (or yarn equivalent)
+- Run `npm update @rails/actioncable @rails/activestorage` to match Rails version
+```
+
+---
+
+## Step 8: Generate Upgrade Summary
+
+Provide a comprehensive summary including all findings from Steps 1-7:
+
+### Version Information
+- Current version: X.Y.Z
+- Latest version: A.B.C
+- Upgrade type: [Patch/Minor/Major]
+
+### Upgrade Complexity Assessment
+
+Rate the upgrade as **Small**, **Medium**, or **Large** based on:
+
+| Factor | Small | Medium | Large |
+|--------|-------|--------|-------|
+| Version jump | Patch only | Minor version | Major version |
+| Breaking changes | None | Few, well-documented | Many, significant |
+| Config changes | Minimal | Moderate | Extensive |
+| Deprecations | None active | Some to address | Many requiring refactoring |
+| Dependencies | Compatible | Some updates needed | Major dependency updates |
+
+### Key Changes to Address
+
+List the most important changes the user needs to handle:
+1. Configuration file updates
+2. Deprecated methods/features to update
+3. New required dependencies
+4. Database migrations needed
+5. Breaking API changes
+
+### Recommended Upgrade Steps
+
+1. Update test suite and ensure passing
+2. Review deprecation warnings in current version
+3. Update Gemfile with new Rails version
+4. Run `bundle update rails`
+5. Update JavaScript dependencies (see JS Dependencies section)
+6. **DO NOT run `rails app:update` directly** - use the selective merge process below
+7. Run database migrations
+8. Run test suite
+9. Review and update deprecated code
+
+### Resources
+
+- Rails Upgrade Guide: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html
+- Rails Diff: https://railsdiff.org/{current}/{target}
+- Release Notes: https://github.com/rails/rails/releases/tag/v{target}
+
+---
+
+
+## When to Use This Skill
+
+Analyze Rails apps and provide upgrade assessments
+
+Use this skill when working with analyze rails apps and provide upgrade assessments.
+## Step 9: Selective File Update (replaces `rails app:update`)
+
+**IMPORTANT:** Do NOT run `rails app:update` as it overwrites files without considering local customizations. Instead, follow this selective merge process:
+
+### 9.1: Detect Local Customizations
+
+Before any upgrade, identify files with local customizations:
+
+```bash
+# Check for uncommitted changes
+git status
+
+# List config files that differ from a fresh Rails app
+# These are the files we need to be careful with
+git diff HEAD --name-only -- config/ bin/ public/
+```
+
+Create a mental list of files in these categories:
+- **Custom config files**: Files with project-specific settings (i18n, mailer, etc.)
+- **Modified bin scripts**: Scripts with custom behavior (bin/dev with foreman, etc.)
+- **Standard files**: Files that haven't been customized
+
+### 9.2: Analyze Required Changes from Railsdiff
+
+Based on the railsdiff output from Step 6, categorize each changed file:
+
+| Category | Action | Example |
+|----------|--------|---------|
+| **New files** | Create directly | `config/initializers/new_framework_defaults_X_Y.rb` |
+| **Unchanged locally** | Safe to overwrite | `public/404.html` (if not customized) |
+| **Customized locally** | Manual merge needed | `config/application.rb`, `bin/dev` |
+| **Comment-only changes** | Usually skip | Minor comment updates in config files |
+
+### 9.3: Create Upgrade Plan
+
+Present the user with a clear upgrade plan:
+
+```
+## Upgrade Plan: Rails X.Y.Z → A.B.C
+
+### New Files (will be created):
+- config/initializers/new_framework_defaults_A_B.rb
+- bin/ci (new CI script)
+
+### Safe to Update (no local customizations):
+- public/400.html
+- public/404.html
+- public/500.html
+
+### Needs Manual Merge (local customizations detected):
+- config/application.rb
+  └─ Local: i18n configuration
+  └─ Rails: [describe new Rails changes if any]
+
+- config/environments/development.rb
+  └─ Local: letter_opener mailer config
+  └─ Rails: [describe new Rails changes]
+
+- bin/dev
+  └─ Local: foreman + Procfile.dev setup
+  └─ Rails: changed to simple ruby script
+
+### Skip (comment-only or irrelevant changes):
+- config/puma.rb (only comment changes)
+```
+
+### 9.4: Execute Upgrade Plan
+
+After user confirms the plan:
+
+#### For New Files:
+Create them directly using the content from railsdiff or by extracting from a fresh Rails app:
+
+```bash
+# Generate a temporary fresh Rails app to extract new files
+cd /tmp && rails new rails_template --skip-git --skip-bundle
+# Then copy needed files
+```
+
+Or use the Rails generator for specific files:
+```bash
+bin/rails app:update:configs  # Only updates config files, still interactive
+```
+
+#### For Safe Updates:
+Overwrite these files as they have no local customizations.
+
+#### For Manual Merges:
+For each file needing merge, show the user:
+
+1. **Current local version** (their customizations)
+2. **New Rails default** (from railsdiff)
+3. **Suggested merged version** that:
+   - Keeps all local customizations
+   - Adds only essential new Rails functionality
+   - Removes deprecated settings
+
+Example merge for `config/application.rb`:
+```ruby
+# KEEP local customizations:
+config.i18n.available_locales = [:de, :en]
+config.i18n.default_locale = :de
+config.i18n.fallbacks = [:en]
+
+# ADD new Rails 8.1 settings if needed:
+# (usually none required - new defaults come via new_framework_defaults file)
+```
+
+### 9.5: Handle Active Storage Migrations
+
+After file updates, run any new migrations:
+
+```bash
+bin/rails db:migrate
+```
+
+Check for new migrations that were added:
+```bash
+ls -la db/migrate/ | tail -10
+```
+
+### 9.6: Verify Upgrade
+
+After completing the merge:
+
+1. Start the Rails server and check for errors:
+   ```bash
+   bin/dev  # or bin/rails server
+   ```
+
+2. Check the Rails console:
+   ```bash
+   bin/rails console
+   ```
+
+3. Run the test suite:
+   ```bash
+   bin/rails test
+   ```
+
+4. Review deprecation warnings in logs
+
+---
+
+## Step 10: Finalize Framework Defaults
+
+After verifying the app works:
+
+1. Review `config/initializers/new_framework_defaults_X_Y.rb`
+2. Enable each new default one by one, testing after each
+3. Once all defaults are enabled and tested, update `config/application.rb`:
+   ```ruby
+   config.load_defaults X.Y  # Update to new version
+   ```
+4. Delete the `new_framework_defaults_X_Y.rb` file
+
+---
+
+
+## When to Use This Skill
+
+Analyze Rails apps and provide upgrade assessments
+
+Use this skill when working with analyze rails apps and provide upgrade assessments.
+## Error Handling
+
+- If `gh` CLI is not authenticated, instruct the user to run `gh auth login`
+- If railsdiff.org doesn't have the exact versions, try with major.minor.0 versions
+- If the app is already on the latest version, congratulate the user and note any upcoming releases
+- If local customizations would be lost, ALWAYS stop and show the user what would be overwritten before proceeding
+
+## Key Principles
+
+1. **Never overwrite without checking** - Always check for local customizations first
+2. **Preserve user intent** - Local customizations exist for a reason
+3. **Minimal changes** - Only add what's necessary for the new Rails version
+4. **Transparency** - Show the user exactly what will change before doing it
+5. **Reversibility** - User should be able to `git checkout` to restore if needed

package/skills/skill-seekers/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: skill-seekers
+description: "-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes."
+source: "https://github.com/yusufkaraaslan/Skill_Seekers"
+risk: safe
+---
+
+# Skill Seekers
+
+## Overview
+
+-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.
+
+## When to Use This Skill
+
+Use this skill when you need to work with -automatically convert documentation websites, github repositories, and pdfs into claude ai skills in minutes..
+
+## Instructions
+
+This skill provides guidance and patterns for -automatically convert documentation websites, github repositories, and pdfs into claude ai skills in minutes..
+
+For more information, see the [source repository](https://github.com/yusufkaraaslan/Skill_Seekers).

package/skills/slack-automation/SKILL.md

@@ -0,0 +1,189 @@
+---
+name: slack-automation
+description: "Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatically."
+requires:
+  mcp: [rube]
+---
+
+# Slack Automation via Rube MCP
+
+Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Slack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `slack`
+- 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 `slack`
+3. If connection is not ACTIVE, follow the returned auth link to complete Slack OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Messages to Channels
+
+**When to use**: User wants to post a message to a Slack channel or DM
+
+**Tool sequence**:
+1. `SLACK_FIND_CHANNELS` - Resolve channel name to channel ID [Prerequisite]
+2. `SLACK_LIST_ALL_CHANNELS` - Fallback if FIND_CHANNELS returns empty/ambiguous results [Fallback]
+3. `SLACK_FIND_USERS` - Resolve user for DMs or @mentions [Optional]
+4. `SLACK_OPEN_DM` - Open/reuse a DM channel if messaging a user directly [Optional]
+5. `SLACK_SEND_MESSAGE` - Post the message with resolved channel ID [Required]
+6. `SLACK_UPDATES_A_SLACK_MESSAGE` - Edit the posted message if corrections needed [Optional]
+
+**Key parameters**:
+- `channel`: Channel ID or name (without '#' prefix)
+- `markdown_text`: Preferred field for formatted messages (supports headers, bold, italic, code blocks)
+- `text`: Raw text fallback (deprecated in favor of markdown_text)
+- `thread_ts`: Timestamp of parent message to reply in a thread
+- `blocks`: Block Kit layout blocks (deprecated, use markdown_text)
+
+**Pitfalls**:
+- `SLACK_FIND_CHANNELS` requires `query` param; missing it errors with "Invalid request data provided"
+- `SLACK_SEND_MESSAGE` requires valid channel plus one of markdown_text/text/blocks/attachments
+- Invalid block payloads return error=invalid_blocks (max 50 blocks)
+- Replies become top-level posts if `thread_ts` is omitted
+- Persist `response.data.channel` and `response.data.message.ts` from SEND_MESSAGE for edit/thread operations
+
+### 2. Search Messages and Conversations
+
+**When to use**: User wants to find specific messages across the workspace
+
+**Tool sequence**:
+1. `SLACK_FIND_CHANNELS` - Resolve channel for scoped search with `in:#channel` [Optional]
+2. `SLACK_FIND_USERS` - Resolve user for author filter with `from:@user` [Optional]
+3. `SLACK_SEARCH_MESSAGES` - Run keyword search across accessible conversations [Required]
+4. `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` - Expand threads for relevant hits [Required]
+
+**Key parameters**:
+- `query`: Search string supporting modifiers (`in:#channel`, `from:@user`, `before:YYYY-MM-DD`, `after:YYYY-MM-DD`, `has:link`, `has:file`)
+- `count`: Results per page (max 100), or total with auto_paginate=true
+- `sort`: 'score' (relevance) or 'timestamp' (chronological)
+- `sort_dir`: 'asc' or 'desc'
+
+**Pitfalls**:
+- Validation fails if `query` is missing/empty
+- `ok=true` can still mean no hits (`response.data.messages.total=0`)
+- Matches are under `response.data.messages.matches` (sometimes also `response.data_preview.messages.matches`)
+- `match.text` may be empty/truncated; key info can appear in `matches[].attachments[]`
+- Thread expansion via FETCH_MESSAGE_THREAD can truncate when `response.data.has_more=true`; paginate via `response_metadata.next_cursor`
+
+### 3. Manage Channels and Users
+
+**When to use**: User wants to list channels, users, or workspace info
+
+**Tool sequence**:
+1. `SLACK_FETCH_TEAM_INFO` - Validate connectivity and get workspace identity [Required]
+2. `SLACK_LIST_ALL_CHANNELS` - Enumerate public channels [Required]
+3. `SLACK_LIST_CONVERSATIONS` - Include private channels and DMs [Optional]
+4. `SLACK_LIST_ALL_USERS` - List workspace members [Required]
+5. `SLACK_RETRIEVE_CONVERSATION_INFORMATION` - Get detailed channel metadata [Optional]
+6. `SLACK_LIST_USER_GROUPS_FOR_TEAM_WITH_OPTIONS` - List user groups [Optional]
+
+**Key parameters**:
+- `cursor`: Pagination cursor from `response_metadata.next_cursor`
+- `limit`: Results per page (default varies; set explicitly for large workspaces)
+- `types`: Channel types filter ('public_channel', 'private_channel', 'im', 'mpim')
+
+**Pitfalls**:
+- Workspace metadata is nested under `response.data.team`, not top-level
+- `SLACK_LIST_ALL_CHANNELS` returns public channels only; use `SLACK_LIST_CONVERSATIONS` for private/IM coverage
+- `SLACK_LIST_ALL_USERS` can hit HTTP 429 rate limits; honor Retry-After header
+- Always paginate via `response_metadata.next_cursor` until empty; de-duplicate by `id`
+
+### 4. React to and Thread Messages
+
+**When to use**: User wants to add reactions or manage threaded conversations
+
+**Tool sequence**:
+1. `SLACK_SEARCH_MESSAGES` or `SLACK_FETCH_CONVERSATION_HISTORY` - Find the target message [Prerequisite]
+2. `SLACK_ADD_REACTION_TO_AN_ITEM` - Add an emoji reaction [Required]
+3. `SLACK_FETCH_ITEM_REACTIONS` - List reactions on a message [Optional]
+4. `SLACK_REMOVE_REACTION_FROM_ITEM` - Remove a reaction [Optional]
+5. `SLACK_SEND_MESSAGE` - Reply in thread using `thread_ts` [Optional]
+6. `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` - Read full thread [Optional]
+
+**Key parameters**:
+- `channel`: Channel ID where the message lives
+- `timestamp` / `ts`: Message timestamp (unique identifier like '1234567890.123456')
+- `name`: Emoji name without colons (e.g., 'thumbsup', 'wave::skin-tone-3')
+- `thread_ts`: Parent message timestamp for threaded replies
+
+**Pitfalls**:
+- Reactions require exact channel ID + message timestamp pair
+- Emoji names use Slack's naming convention without colons
+- `SLACK_FETCH_CONVERSATION_HISTORY` only returns main channel timeline, NOT threaded replies
+- Use `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` with parent's `thread_ts` to get thread replies
+
+### 5. Schedule Messages
+
+**When to use**: User wants to schedule a message for future delivery
+
+**Tool sequence**:
+1. `SLACK_FIND_CHANNELS` - Resolve channel ID [Prerequisite]
+2. `SLACK_SCHEDULE_MESSAGE` - Schedule the message with `post_at` timestamp [Required]
+
+**Key parameters**:
+- `channel`: Resolved channel ID
+- `post_at`: Unix timestamp for delivery (up to 120 days in advance)
+- `text` / `blocks`: Message content
+
+**Pitfalls**:
+- Scheduling is limited to 120 days in advance
+- `post_at` must be a Unix timestamp, not ISO 8601
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to IDs before operations:
+- **Channel name -> Channel ID**: `SLACK_FIND_CHANNELS` with `query` param
+- **User name -> User ID**: `SLACK_FIND_USERS` with `search_query` or `email`
+- **DM channel**: `SLACK_OPEN_DM` with resolved user IDs
+
+### Pagination
+Most list endpoints use cursor-based pagination:
+- Follow `response_metadata.next_cursor` until empty
+- Set explicit `limit` values (e.g., 100-200) for reliable paging
+- De-duplicate results by `id` across pages
+
+### Message Formatting
+- Prefer `markdown_text` over `text` or `blocks` for formatted messages
+- Use `<@USER_ID>` format to mention users (not @username)
+- Use `\n` for line breaks in markdown_text
+
+## Known Pitfalls
+
+- **Channel resolution**: `SLACK_FIND_CHANNELS` can return empty results if channel is private and bot hasn't been invited
+- **Rate limits**: `SLACK_LIST_ALL_USERS` and other list endpoints can hit HTTP 429; honor Retry-After header
+- **Nested responses**: Results may be nested under `response.data.results[0].response.data` in wrapped executions
+- **Thread vs channel**: `SLACK_FETCH_CONVERSATION_HISTORY` returns main timeline only; use `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` for thread replies
+- **Message editing**: Requires both `channel` and original message `ts`; persist these from SEND_MESSAGE response
+- **Search delays**: Recently posted messages may not appear in search results immediately
+- **Scope limitations**: Missing OAuth scopes can cause 403 errors; check with `SLACK_GET_APP_PERMISSION_SCOPES`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Find channels | `SLACK_FIND_CHANNELS` | `query` |
+| List all channels | `SLACK_LIST_ALL_CHANNELS` | `limit`, `cursor`, `types` |
+| Send message | `SLACK_SEND_MESSAGE` | `channel`, `markdown_text` |
+| Edit message | `SLACK_UPDATES_A_SLACK_MESSAGE` | `channel`, `ts`, `markdown_text` |
+| Search messages | `SLACK_SEARCH_MESSAGES` | `query`, `count`, `sort` |
+| Get thread | `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` | `channel`, `ts` |
+| Add reaction | `SLACK_ADD_REACTION_TO_AN_ITEM` | `channel`, `name`, `timestamp` |
+| Find users | `SLACK_FIND_USERS` | `search_query` or `email` |
+| List users | `SLACK_LIST_ALL_USERS` | `limit`, `cursor` |
+| Open DM | `SLACK_OPEN_DM` | user IDs |
+| Schedule message | `SLACK_SCHEDULE_MESSAGE` | `channel`, `post_at`, `text` |
+| Get channel info | `SLACK_RETRIEVE_CONVERSATION_INFORMATION` | channel ID |
+| Channel history | `SLACK_FETCH_CONVERSATION_HISTORY` | `channel`, `oldest`, `latest` |
+| Workspace info | `SLACK_FETCH_TEAM_INFO` | (none) |