Loading...
Loading...
Found 1,409 Skills
Build and edit live Superwall paywalls from the CLI. Attach to a running browser editor session using a pairing code, list the tools the browser exposes right now, and invoke them. Covers native sw-* elements, editing workflow, design standards, and the attach/call/release lifecycle. Use whenever the user wants to design, build, modify, or review a Superwall paywall, onboarding, or web2app flow.
Hot-reload Go apps with cosmtrek/air during development. Use when setting up dev workflows for Go HTTP servers, configuring .air.toml, or debugging hot-reload issues with SQLite, port binding, or file watchers.
Подробная русскоязычная справка по Open WebUI: архитектура, авторизация, функции, пайплайны, API, RAG, масштабирование, отладка и скрытые возможности. Используй этот скилл при любых вопросах об Open WebUI — как он устроен, как развернуть, настроить авторизацию (OAuth, LDAP, JWT), написать функцию или пайплайн, подключить модель (Ollama, OpenAI), настроить RAG/knowledge base, масштабировать на production, отладить проблему. Также используй при написании кода для Open WebUI: функции (filter, pipe, action), пайплайны, конфигурации, docker-compose.
Use when an n8n workflow isn't working, errors appear, results don't match what was expected, or the user says "this isn't working." Triggers on errors, unexpected output, "it's not working", "why is this happening", "the workflow stopped", failure investigation, or any debugging context.
Investigate Kubernetes workload, node, and control-plane issues using OTel telemetry (EDOT). Use when diagnosing pod failures (CrashLoopBackOff, OOMKilled, Error), node pressure, resource exhaustion, image pull failures, admission rejections, autoscaling anomalies, or correlating K8s state with application signals. OTel ingest path only — the legacy ECS Kubernetes integration shape is out of scope.
SOP for Vehicle Entry/Exit Operation Process of AIKE Smart Parking Open Platform (End-to-end Orchestration for Entry/Exit). This skill is applicable when users want to complete the full entry/exit of a vehicle, simulate the real physical entry/exit process, run through the entire link of 'Supplement/Capture Entry → Correction' or 'Exit Capture → Correction → Fee Inquiry → Payment', or ask questions like 'How does a vehicle enter/exits the parking lot?', 'Entry/exit process', 'Entry/exit SOP', 'How to move a vehicle into/out of the parking lot', 'Simulate vehicle entry/exit', or encounter stuck/debugging issues during entry/exit (e.g., vehicle fails to enter after capture or correction, capture returns error code 908, unsure how to proceed to the next step). This skill is a cross-domain orchestration layer that connects multiple commands from parking (supplement/correction/inventory), device (capture), and trade (fee inquiry/payment), and clarifies cross-command hard constraints (paired exit, capture device, channel release mode, token validity) and failure handling. Boundary: For querying a single record, checking on-site vehicles, locking vehicles, or calling a single command, please directly use the corresponding domain skills openydt-record / openydt-device / openydt-billing instead of this process skill.
Set up, configure, and troubleshoot Salesforce Code Analyzer for any project. Handles installation, prerequisite checks, diagnosing broken setups, creating and editing code-analyzer.yml overrides, engine-specific settings, ignore patterns, severity overrides, and CI/CD pipeline setup. TRIGGER when: user says 'set up code analyzer', 'configure code analyzer', 'install code analyzer', 'code analyzer not working', 'fix my setup', 'scan is failing', 'check my setup', 'is code analyzer installed', 'enable/disable engine', 'exclude files', 'change severity', 'set up GitHub Actions', 'set up CI/CD', 'add code analyzer to pipeline', 'make pipeline fail', 'update my workflow', 'quality gate', 'fail on violations', 'scan changed files only', 'add SARIF', 'code-analyzer.yml', 'ESLint config', 'increase SFGE memory', or reports errors running Code Analyzer. DO NOT TRIGGER when: user wants to run a scan (use running-code-analyzer), fix violations, explain rules, create custom rules, or suppress violations.
Debug Docker containers and containerized applications. Diagnose deployment issues, container lifecycle problems, and resource constraints.
Guide for recovering lost Git commits, resolving detached HEAD states, and fixing common Git repository issues. This skill should be used when users need help recovering from Git mistakes such as lost commits, detached HEAD situations, accidental resets, or when commits appear to be missing from branches.
Create Obsidian-compatible Mermaid diagrams. Prefer square layouts (TB + subgraph LR), avoid markdown in labels. Use when creating flowcharts, sequence diagrams, or any Mermaid diagrams in markdown files.
This skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.
This skill should be used when configuring Claude, setting up MCP servers, or when "settings.json", "claude_desktop_config", "MCP server", or "Claude config" are mentioned.