Loading...
Loading...
Found 5,656 Skills
Automate Shipengine tasks via Rube MCP (Composio). Always search tools first for current schemas.
Reviews PR changes against issue technical details and acceptance criteria, posts concise outcomes to PR and issue tracker, and routes autonomous next steps.
Send a team announcement via both Gmail and a Google Chat space.
Share Google Drive files with all attendees of a Google Calendar event.
Chain document operations into reusable pipelines
Debug failing Power Automate cloud flows using the FlowStudio MCP server. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app
Implement a task with automated LLM-as-Judge verification for critical steps
How to work in artist directories — including creating, enumerating, and editing them. Use when creating or onboarding a new artist ("create artist", "onboard X", "add this artist", "set up a new artist") — this skill scaffolds the artist's `RECOUP.md` checklist file and drives the multi-step setup from it. Use when adding or updating artist context (identity, brand, voice, audience), adding songs, organizing files inside an artist directory, or figuring out where something belongs. Also use when the account asks inventory questions like "what artists do I have", "list my artists", "which orgs am I in", "what's in this sandbox" — the filesystem tree is the authoritative answer. And use when the account mentions an artist by name and the task involves their files, context, or content — even if they don't say "artist directory." This includes tasks like researching an artist, creating content for an artist, updating an artist's brand, or adding a face guide.
Information Question Generator. Given an article, paper, or book, extract its core viewpoints into Q-A pairs — Questions get straight to the point, no textbook-style phrasing; Answers are concise and clear, with formalized conclusions and complete logical chains. As readers follow the Q chain, each Answer drives home a key point, reproducing the author's entire reasoning process. Activate when the user says '问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa', or shares an article, paper, or book and requests Q-A extraction. This tool triggers when the user wants ideas extracted not as a summary but as a sequence of incisive questions paired with answers. NOT FOR FAQ generation, glossary creation, or comprehension quizzes — this is intellectual scaffolding, not a study aid.
Use when working on Laminar demands via the remote Laminar MCP and you see wrong or empty client/product scope, plans from source-context lists without per-id loads, needless raw transcripts, same-step or same-release story-map peers, anchored ADR conflicts, MCP transitions/assignments, broken or silent MCP, or mentions of Laminar MCP, demands, TAL-* ids, story map, anchored or source context, or Laminar handoff.
Record a reusable flow (scripted sequence of MCP tool calls) that can be replayed later with a single command. Use when the user asks to create, record, or build a flow, or to script a sequence of device actions.
Opens a new jackin' feature or idea as a roadmap item draft plus an early pull request, without writing any code. Use when the operator runs /jackin-dev:propose.