kklouzal

MikroTik RouterOS documentation-first workflow for MikroTik-specific questions, troubleshooting, command planning, live CLI/API work, config review, log analysis, security review, performance tuning, and diagnostics. Use when the request is clearly about MikroTik or RouterOS: MikroTik devices, RouterOS, RouterBOARD, CAPsMAN, WinBox, RouterOS CLI/API/SSH access, or networking topics specifically in a MikroTik context such as firewall, NAT, filter/raw/mangle, bridge, switch, VLAN, DHCP, DNS, queues, wireless/WiFi, routing, packet flow, connection tracking, or device management. Do not use for generic networking theory, generic firewall design, or generic Linux router/admin work unless the MikroTik/RouterOS context is explicit.

Multi-provider anime → MyAnimeList sync and recommendations skill with guarded auth, review-queue triage, health checks, bootstrap auditing, and user-systemd daemon support. Currently supports Crunchyroll and HIDIVE as source providers. Use when installing, auditing, operating, or troubleshooting MAL-Updater on an OpenClaw host.

Use for SherpaDesk-related requests: ticket lookup, support-history retrieval, account/user/technician analysis, stale-ticket review, workload questions, operational reporting, and open-ended natural-language questions about SherpaDesk data. This skill is a local SherpaDesk backend plus OpenClaw query layer: it requires SherpaDesk API credentials for live setup, creates workspace-local runtime state under `.SherpaMind/`, and may install an optional user-level background service. Trigger when the user mentions SherpaDesk or asks about tickets, support issues, clients/accounts, technicians, resolution history, recurring incidents, backlog, response timing, or similar support-operations analysis.

vLLM documentation-first workflow for vLLM-specific questions, troubleshooting, command planning, OpenAI-compatible serving behavior, model-loading/runtime behavior, scheduler/prefix-caching/chunked-prefill semantics, quantization and kernel-path checks, multimodal/tool-calling and Responses/OpenAI surface review, build/install/source-tree work, and diagnostics when the actual product/runtime layer is vLLM. Use when the request is clearly about vLLM itself: the `vllm` Python package/CLI, `vllm serve`, `vllm.entrypoints.openai.api_server`, OpenAI-compatible endpoints implemented by vLLM, engine arguments, cache/scheduler behavior, tensor-parallel/pipeline-parallel/expert-parallel settings, paged attention, prefix caching, chunked prefill, speculative decoding, structured outputs, tool calling, reasoning parsers, model support, quantization backends, flash-attention/FlashInfer/XFormers/Triton/kernel selection, or vLLM source build/runtime behavior where vLLM-specific semantics matter. Do not use for generic LLM

Kubernetes documentation-first workflow for Kubernetes-specific questions, troubleshooting, command planning, cluster operations, workload/resource behavior, networking, storage, scheduling, security, and diagnostics. Use when the request is clearly about Kubernetes itself: the `kubectl` CLI, Kubernetes API objects, pods, deployments, services, ingress, config maps, secrets, volumes, nodes, scheduling, RBAC, controllers, CRDs, Helm-free core Kubernetes behavior, or cluster/runtime behavior where Kubernetes- specific semantics matter. Do not use for generic Linux administration, generic container theory, generic cloud architecture, or Docker-only questions unless the Kubernetes layer is specifically what is being discussed or debugged.

Docker documentation-first workflow for Docker-specific questions, troubleshooting, command planning, image/build work, container/runtime operations, Compose behavior, networking, volumes, registries, and diagnostics. Use when the request is clearly about Docker itself: the `docker` CLI, Docker Engine, Dockerfiles, BuildKit/buildx, Docker Compose, images, containers, registries, volumes, networks, contexts, rootless Docker, or Docker Desktop/Engine behavior where Docker-specific semantics matter. Do not use for generic Linux administration, generic OCI/container theory, generic shell work, or Kubernetes/orchestration questions unless the Docker layer is specifically what is being discussed or debugged.

GLSL language/specification workflow for GLSL-specific questions, shader authoring and review, exact syntax and semantic lookup, built-in and qualifier reference, interface/layout reasoning, stage-specific behavior checks, version/extension rules, and compiler-error triage when the actual language layer is GLSL. Use when the request is clearly about GLSL itself: GLSL/OpenGL Shading Language syntax, shader source using `#version`, `layout(...)`, `in`/`out`, `uniform`, `buffer`, samplers/images, built-in variables/functions, interface blocks, stage-specific shader code, or `glslangValidator`/GLSL compiler errors in a GLSL context. Do not use for HLSL, WGSL, MSL, Slang, SPIR-V assembly, generic rendering questions, or Vulkan API/spec questions unless the language layer being debugged or discussed is specifically GLSL.

Vulkan specification/reference workflow for Vulkan-API-specific questions, exact command and structure semantics, valid-usage and VUID lookup, synchronization reasoning, pipeline/resource setup, extension/feature checks, limits/formats/capabilities review, and code review in a Vulkan API context. Use when the request is clearly about Vulkan itself: `Vk*` types, `vk*` commands, VUIDs, instance/physical-device/logical-device setup, swapchains, queues, command buffers, descriptors, render passes or dynamic rendering, pipelines, memory/resources, synchronization, SPIR-V in a Vulkan pipeline context, or extension/feature behavior. Do not use for generic graphics programming, engine-level rendering design, shader-language-only questions, OpenGL, Direct3D, Metal, CUDA, or generic shader authoring unless the Vulkan API/spec layer is materially involved.

Ubuntu documentation-first workflow for Ubuntu-specific questions, maintenance, updates, upgrades, package management, system administration, service troubleshooting, networking, storage, logs, release behavior, and diagnostics. Use when the request materially depends on Ubuntu or Ubuntu-specific tooling/behavior such as Ubuntu release behavior, `apt`/`apt-get`/`dpkg`/`snap`, `systemd`/`systemctl`/`journalctl`, Netplan, NetworkManager, package repair, repository/key issues, service failures, boot issues, mounts/`fstab`, permissions, users/groups, or non-trivial Ubuntu maintenance/troubleshooting. Do not use for generic shell, git, Python, Docker, or Linux questions unless Ubuntu-specific semantics matter.

ESPHome configuration/component documentation-first workflow for ESPHome-specific questions, YAML/config authoring, config review, component selection, substitutions/packages usage, device definitions, secrets handling, OTA/update planning, build/compile troubleshooting, sensor/actuator tuning, logs, diagnostics, and live dashboard or node maintenance. Use when the request is clearly about ESPHome or an ESPHome node/config: ESPHome/esphome, ESP32/ESP8266 in an ESPHome context, ESPHome dashboards, packages, substitutions, `secrets.yaml`, OTA flashing, compile errors, pin assignments, Wi-Fi provisioning, or node troubleshooting. Also use when ESPHome YAML sections such as `sensor:`, `binary_sensor:`, `switch:`, `light:`, `output:`, `display:`, `climate:`, `cover:`, `wifi:`, `api:`, `ota:`, `logger:`, `web_server:`, `esp32:`, `esp8266:`, `packages:`, or `substitutions:` appear in an ESPHome configuration context. Do not use for generic YAML, generic embedded/microcontroller programming, generic Home Assistant au

OpenClaw product/runtime/configuration documentation-first workflow for OpenClaw-specific questions, troubleshooting, command planning, configuration review, automation design, cron/heartbeat behavior, gateway/runtime diagnostics, skill loading/configuration, channel/session/node behavior, security, and operational guidance. Use when the request is specifically about OpenClaw itself: the `openclaw` CLI, gateway, agents, sessions, channels, nodes, plugins, pairings, Control UI/ dashboard, `openclaw.json`, cron jobs, heartbeats, approvals, sandboxing, provider routing, messaging behavior, or OpenClaw skill loading/gating/install/update. Do not use for generic agent prompting, generic SKILL.md/AGENTS.md authoring, generic Linux/systemd administration, or generic chat-assistant design unless the question is specifically about OpenClaw behavior or configuration.