Loading...
Loading...
Found 5,760 Skills
ScreenshotOne integration. Manage Screenshots, Usages. Use when the user wants to interact with ScreenshotOne data.
BTCPay Server integration. Manage data, records, and automate workflows. Use when the user wants to interact with BTCPay Server data.
Install and bootstrap a Coder (coder/coder) deployment end-to-end from the CLI without the web UI. Covers quick-start (one machine, auto-tunnel URL) and production (real domain, TLS, wildcard, OIDC, external provisioner). Drives GitHub device-code on fresh deployments to sign the first admin in without a browser, falls back to email/password for scripted runs, pushes a starter template, and optionally creates a first workspace. Activate when the user says: "install Coder", "set up Coder", "deploy Coder", "bootstrap Coder", "run Coder in Docker / on Kubernetes / on a VM", "Coder on AWS / GCP / Azure", "put Coder behind HTTPS / Caddy / nginx / cert-manager", "wildcard domain", "headless / non-interactive setup", "create the first admin from the CLI", "push a starter template", or "create my first workspace". Also activate for /coder:setup. Do NOT activate for upgrading an existing deployment, editing an existing template, debugging a running server, or configuring OIDC / custom OAuth on a running deployment.
Full-Process Web Novel/Story World Builder, suitable for users' overall novel writing needs such as saying "I want to write a novel", "Write a web novel", "Create a novel from scratch", "Help me write a novel of XX genre", "I want to write a novel", "Give me the entire novel creation process", "Auto-write a novel", "One-stop novel creation service", "Help me finish a novel", "How to write a novel with only an idea", etc. It automatically coordinates the full process of topic selection, outline design, writing, review, and polishing. Even if you only have a rough idea, it can help you complete a full work from 0 to 1 and build a unified story world. **All chapter-level operations are processed in parallel by sub-Agents, with each Agent responsible for a maximum of 3 chapters**
PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
Maravilla Cloud durable workflows — replay-based, multi-step processes that survive restarts. Use whenever you need sleeps spanning minutes/hours/days, multi-step pipelines where each step's output feeds the next, waiting for external events, or strict step-history audit. `defineWorkflow` from `@maravilla-labs/functions/workflows/runtime` with `step.run`, `step.sleep`, `step.sleepUntil`, `step.waitForEvent`, `step.invoke`.
Use when an idea reaches ApprovedForProject status to create project, plan structure, and commit PLAN.md to repository. Merges project creation and planning into atomic operation.
BrowserStack integration. Manage data, records, and automate workflows. Use when the user wants to interact with BrowserStack data.
Create a new SigNoz alert rule from a natural-language intent — threshold, anomaly, log-volume, error-rate, latency, or absent-data alerts across metrics, logs, traces, and exceptions. Make sure to use this skill whenever the user says "alert me when…", "notify me if…", "set up monitoring for…", "page me on…", "create an alert for…", or asks for a new alert/notification rule, even if they don't say the word "alert" explicitly. Also use it when someone asks to be notified about error rates, latency spikes, log volume, CPU/memory pressure, or anomalous behavior on a service or host.
Payrexx integration. Manage data, records, and automate workflows. Use when the user wants to interact with Payrexx data.
Batch-translate content files using Gemini CLI as a subagent, with Claude orchestrating quality and validation
Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with *Test.cls / *_Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use generating-apex), Agentforce agent testing (use testing-agentforce), or Jest/LWC tests (use generating-lwc-components).