Loading...
Loading...
Found 2,026 Skills
Authenticate with AEM Edge Delivery Services Config Service API. Opens a browser window for Adobe ID login and captures the auth token when browser is closed. Use when generating guides/documentation that require API access.
Discover and cache all installed ComfyUI models, custom nodes, and system capabilities. Works online (API queries) and offline (directory scanning). Use before generating workflows to verify available resources.
Trigger this skill when building applications with Gemma or for general knowledge inquiries related to Gemma models (e.g. prompt structure, capabilities). Covers model selection, development workflows, and deployment best practices.
Use when users need Rust quantitative SDK or TQSDK Rust capabilities: real-time market data/quote/market depth/K-line/tick, product/contract list, main continuous contract/continuous contract, option chain, contract specification, metadata/direct query, historical data download/cache/CSV/Greeks, trading account/order placement/order cancellation/order status, TargetPosTask/risk control/multi-account/strategy execution, low-latency trading desk, stream/fan-out, replay/backtest/live-sim-replay; also applicable when agents need real-time or historical quantitative data, transaction execution substrate, or trading desk capabilities, even if TQSDK is not explicitly mentioned.
Multi-step video annotation pipeline that turns raw videos into Chain-of-Thought training data — multi-level captions, structured descriptions, and QA pairs (MCQ, binary, open-ended) with reasoning traces, via VLM/LLM distillation. Use when the user wants to "create video training data", "generate video QA datasets", "build CoT reasoning traces from videos", "auto-label videos", or run the video_reasoning_annotation pipeline. Triggers include "video annotation", "video CoT", "video QA", "chain-of-thought", "video captioning pipeline", "video distillation".
QA a PR's UI change in a real browser through the configured browser-provider descriptor — first ensuring the PR has been reviewed (invoking om-auto-review-pr when it has not), then capturing screenshots and a pass/fail report, and optionally posting tracker evidence or self-QA labels without modifying source. Also runs in a local, tracker-less mode against the current worktree.
Routing skill of last resort. Takes a plain-language QA situation and names the right 1-2 skills to use and in what order. Use ONLY when the request does not match any other skill's trigger phrases. Use when: "which skill should I use," "where do I start," "I'm not sure what to test," "/qa-do," or any vague QA situation that doesn't map to one skill. Not for: bootstrapping a brand-new project with no QA — use qa-start. Not for: capturing project setup/context — use qa-project-context. If the request clearly matches another skill, invoke that skill directly instead of routing through here. Related: qa-start, qa-project-context, test-strategy.
Maintaining the story knowledge base: creating, updating, and organizing wiki-style reference pages in kb/. Use when capturing finalized story knowledge, updating character profiles, documenting world mechanics, or restructuring the kb.
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
Use the run-workflow MCP to discover, compose, execute, publish, and save Adobe Firefly workflows. TRIGGER when: user asks what actions are available, what the MCP can do, how to process images/video/3D via workflow, wants to build/run/save/publish a workflow, OR pastes any workflow/batch/execution ID. BARE ID (UUID/workflowId/batchId) = INSPECT ONLY — call inspect_run, NEVER run_workflow_submit. ALWAYS call list_actions first for capability/discovery questions. DO NOT TRIGGER for direct Firefly API calls without MCP (use firefly-api-specs).
Use to plan and produce a full batch of social media content for a period — a week or a month — in one session: strategically balanced, on-brand, mapped to a calendar, and ready to schedule. Run when the user says "plan my content," "a month of posts," "batch my content," "plan the week," "fill my calendar," or wants many posts planned at once in one sitting. Reads brand-profile, voice, and content-pillars first, and produces a brief for each post that the content skills (caption-writer, reels-script, hook-writer) execute. As a BRIDGE skill it then confirms and hands the batch to scheduling-and-queue. Builds a balanced mix — never all-promotion — matched to the user's real capacity. Suggests cadence but does not claim analytics-based timing (WoopSocial has no analytics surface yet). For the ongoing recurring system — which pillars/formats post on which days, the living "content calendar" — use content-calendar; this skill fills one specific period of that system with actual post briefs.
Use to write a TikTok script — a native, sound-aware short-video script optimized for TikTok's discovery engine (the FYP), built around a brutal 1-second hook, watch-time, and rewatches. Run when the user says "TikTok script," "TikTok video," "script for TikTok," "make a TikTok," "storytime," "TikTok hook," or wants short-form video for TikTok specifically. Reads brand-profile and voice first; rides a trending sound/format where it genuinely fits (live trend research goes to trend-jacking); structures for completion + rewatch; optimizes for TikTok search; outputs a production doc (shot - on-screen text - spoken - sound - timing) plus a Veo prompt pack for faceless/b-roll shots (native filming often beats AI on TikTok). For Instagram Reels use reels-script; for YouTube Shorts use youtube-shorts; for the platform-agnostic scripting craft use short-form-video-script; hands caption to caption-writer and scheduling to scheduling-and-queue.