Loading...
Loading...
Found 85 Skills
Configure OpenClaw gateway integration for waking external automations and AI agents on hook events
Decentralized git for AI agents and humans. Use when the user wants to create repositories, push code, open pull requests, review and merge PRs, manage issues, create or claim bounties, delegate tasks to other agents, register human-readable names on Base L2, or interact with the gitlawb decentralized git network. Supports cryptographic DID identities, Ed25519-signed pushes, UCAN capability delegation, libp2p networking, and 31+ MCP tools for AI agent integration. Do NOT use for GitHub, GitLab, or other centralized git hosts.
Terminal-first Twitter/X CLI for reading feeds, bookmarks, search, and posting tweets without API keys
Run a repo-wide cross-cutting governance audit via the pm-skill-auditor sub-agent. Dispatches natively on Claude Code with the pm-skills plugin (invokes @agent-pm-skill-auditor); on non-Claude clients (Codex CLI, Cursor, Windsurf, Copilot, Gemini CLI) reads subagents/pm-skill-auditor.md and executes the system prompt inline. Returns a layered audit report (full findings + Status Summary prose + Status YAML envelope per master plan D26) with cross-cutting findings graded P0/P1/P2/P3 plus aggregate counter audit and validator results table.
Model Context Protocol development expert. Use when creating MCP servers, clients, or tools that enable AI agents to interact with external systems, APIs, and development environments.
Guidance for the bundled Zoom MCP connectors. Use after routing to an MCP workflow when planning or troubleshooting tool-based access to meetings, recordings, meeting assets, or transcripts. Route Zoom Docs requests to the dedicated Docs MCP server and Whiteboard-specific requests to `zoom-mcp/whiteboard`.
MCP server for Xiaohongshu (Little Red Book) - search, publish posts, manage interactions, and automate content operations
Feishu Real-time Event Subscription (WebSocket). Use `event list` to view supported EventKeys; `event schema` to check event payload/scope; `event consume` to start long-connection subscription, where event streams are written to stdout in NDJSON format (blocking, one process subscribes to one EventKey); `event status` to view active local consume processes; `event stop` to terminate consume processes by PID / EventKey / --all. Supports over 22 EventKeys (including IM message receive/read/recall/reaction, group member changes, contact employee changes, calendar changes, cloud disk title/collaborator changes, approval instances and tasks, VC meeting start/end). Status files: ~/.feishu-cli/events/<app_id>/bus.json + flock file lock + WebSocket auto-reconnect. This skill is applicable when users request "listen to Feishu events", "real-time message event reception", "approval callback subscription", "event stream", "WebSocket long-connection listening", "event consume", "event list / schema / status / stop", "AI Agent bot real-time response". Note: This skill only handles subscription; for event webhook business logic (pushing to Feishu messages/writing to multidimensional tables), please use with feishu-cli-msg / feishu-cli-bitable.
MCP server for real-time Three.js scene inspection, material editing, shader debugging, and performance monitoring from AI agents
Official Lark/Feishu plugin for OpenClaw that enables AI agents to interact with Lark workspaces including messages, docs, bases, calendars, and tasks
Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send the image", Merge losing binary, or a CDN for chat images. Covers the $binary vs $json split, reading/writing binary, keeping binary alive across transforms with Merge, the agent-tool binary boundary, and the CDN/URL requirement for chat surfaces.
Creates implementation-ready blueprints for new software products, features, apps, and internal tools. Use when starting a greenfield project, major feature, or technical handoff that needs PRD, TRD, architecture, schema, security, modules, rules, phases, design, and memory docs.