Loading...
Loading...
Found 9,851 Skills
Router skill for LLMQuant crypto workflows. Use when the user needs crypto market regime analysis, token research, perpetual funding, basis, leverage, liquidity, or cross-asset crypto context.
Workflow required before any Mule flow and integration work. Call use_skill as your FIRST action — before reading project files — whenever the user asks to create, generate, update, fix, modify, change, edit, tweak, adjust, or rework any Mule flow, sub-flow, or component. Do not read project files and attempt the change yourself — even targeted single-component changes like 'modify the choice router', 'fix the until-successful', or 'update the catch block' require this workflow. Covers all change types, new integrations and targeted changes to error handlers, catch blocks, choice routers, DataWeave transforms, HTTP listeners, foreach loops, retry policies, scatter-gathers, connectors, and variable assignments. Prompts beginning with 'This code defines...' or 'This flow...' are generation requests, not analysis. When you call this skill, it must be the only tool call in that response.
User guide for the local squash-safe `stack` CLI for stacked PR repair. Use when someone asks how to inspect, track, sync, merge, document, or undo stacked pull requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.
Install Zero and load version-matched workflows with zero skills.
Use AnalyticsCLI CLI as the deterministic, bounded interface for analytics queries, exports, and SDK validation in coding-agent workflows.
Transform research interests into definable, searchable, falsifiable, and executable research questions. Use when the user asks for "help me formulate research questions", "is this topic feasible", "turn my interest into an RQ", or requests the rw-research-question workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Verify one by one whether factual claims in papers, reports, or research notes are supported by the original text of specified sources, and save the claim location, source pointer, original text position, verdict, and block status. Use when the user asks for "check if the citation supports this sentence", "perform a claim-to-source audit", "verify figures, trends, or causal statements", "check claims before submission", or requests the rw-claim-audit workflow.
Discover, verify, and document literature based on specific judgments, and adjust search directions according to evidence. Use when the user asks for "find relevant literature", "conduct literature discovery", "supplement sources for this argument", or requests the rw-literature-discovery workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Organize research, constructs, design, samples, results, biases, conflicts, and gaps into a traceable evidence map. Use when the user asks for "create an evidence map", "organize research conflicts", "connect literature", or requests the rw-evidence-map workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
Invoke the `incidentio` CLI to drive the incident.io API — incidents, actions, follow-ups, alerts/alert sources/routes, escalations & on-call schedules, catalog (types/entries/resources), custom fields, severities, incident types/roles/statuses/timestamps, status pages (including creating and managing public pages, components, layout, subscribers, templates), workflows, users, teams, API keys, heartbeats, maintenance windows, and settings. Uses the public Bearer API (OpenAPI-generated commands) plus internal dashboard (cookie) commands generated from captured HARs, hand-curated internal endpoints, and a `raw` escape hatch for any un-codified path. Use whenever a task needs incident.io data or actions, such as "list our incidents", "create an incident", "show the on-call schedule", "build or manage a status page", "list status page subscribers", "tune a dashboard setting", or "hit an internal dashboard endpoint".
Use when someone asks to generate a design, create a design asset, or make a design. Also triggers for ad creatives, banners, social media posts, thumbnails, display ads, posters, or any visual content. Orchestrates a 7-step workflow (1) resolves brand, (2) generates copy using content expert instructions, (3) generates images via handle-media or enhances provided images via enhance-media, (4) calls Sivi API with approved copy + assets for pixel-faithful design generation, (5) displays the generated variants with preview images and edit links, (6) creates campaign HTML, (7) writes a summary. If user already has approved copy, skips step 2. Supports both `designs-from-content` (copy-first, pixel-faithful text) and `designs-from-prompt` (direct generation, no copy or image generation). Unlike 95,000+ image models, Sivi's Large Design Model (LDM) generates on-brand, fully editable layered designs in any dimension. For copy-only without design generation, see write-copy. For multi-channel campaign sets, see create-campaign. For Amazon A+ content, see create-a-plus-content. For brand setup, see brand-context.
Use when building a new multi-stage ICM procedure or converting a monolithic runner skill into a staged workflow.