Skill UI

A utility for interacting with the Lark/Feishu communication directory. It allows users to search for employees by name or email to obtain an open_id, or use an open_id to retrieve comprehensive profile data, including department, contact details, status, and signature. Ideal for preparing information before sending messages or scheduling events. Note that department tree traversal and organizational structure mapping require native OpenAPI calls.

OpenViking Code Repository Search exposes `ov` terminal commands for scoped semantic, keyword, and glob searches across viking:// resources, lets you read directory summaries/files, and manage indexed repositories (add/remove) with documented error handling.

This skill allows agents to ingest external resources (local files, URLs, repositories) using `ov add-resource`, and to create long-lasting searchable memories from conversations using `ov add-memory`. It is essential for building a comprehensive, persistent knowledge base for the OpenViking context database, ensuring that learned insights and external data remain available across sessions and interactions. Use when external knowledge injection or context persistence is required.

This tool analyzes specification files to extract all defined requirements and cross-references them with the current codebase implementation status. It systematically checks for unimplemented features, searches existing GitHub issues to prevent duplicates, and automatically generates detailed issues using a standardized feature request template. It is essential for robust product management, ensuring every defined requirement is tracked and scheduled for development.

This comprehensive toolkit provides full automation capabilities for Dropbox operations. Users can search for files and folders by content or metadata, upload and download large files, manage folder structures (create, move, delete), and generate secure sharing links. It streamlines collaboration and data transfer workflows, making it essential for automated business processes and cloud file management.

A lightweight, standalone integration for Google Drive that provides full read/write access without requiring a dedicated MCP server. It allows scripts to perform comprehensive file and folder operations, including searching, uploading, downloading, moving, renaming, and managing content within a Google Workspace account. Ideal for automating workflow tasks that depend on Google Drive data.

A skill for AI agents to maintain persistent task planning via Markdown files (task_plan.md, findings.md, progress.md). Lifecycle hooks inject project context automatically, supporting multi-step tasks with 5+ tool calls. Optional session catch-up can inspect local metadata. Suitable for research and complex workflows.

This toolkit provides comprehensive automation capabilities for Box cloud storage. It allows users to manage the entire document lifecycle, including file uploading and downloading, deep content searching using metadata filters, creating and modifying folders, and managing collaboration permissions. Ideal for integrating Box into automated business workflows, ensuring documents are always accessible and organized.

Use Rube MCP and Composio’s LinkedIn toolkit to publish posts, manage profile/company info, handle images, comments, and deletions through authenticated workflows while always refreshing tool schemas via RUBE_SEARCH_TOOLS.

This skill provides comprehensive automation for managing OneDrive file lifecycles. Users can perform advanced operations including searching across metadata and content, uploading and downloading files, organizing folders, creating share links, and granularly managing permissions for specific users. It utilizes a structured workflow approach via Rube MCP, making it ideal for automating business processes involving cloud document storage and collaboration.

Continuous file-based planning system for multi-step AI agents. Maintains task_plan.md, findings.md, and progress.md files on disk, injecting project-specific planning context into lifecycle hooks. Auto-restore reads only project planning files. Used for research or work requiring 5+ tool calls.

Persist multi-step agent work using markdown files (task_plan.md, findings.md, progress.md) as disk memory. Lifecycle hooks inject plan context, support session recovery, and keep long research or tool-heavy tasks on track.