Total 31,105 skills, DevOps & Cloud Services has 1922 skills
Showing 12 of 1922 skills
Build PromQL, LogQL, TraceQL queries for Perses panels. Validate query syntax, suggest optimizations, handle variable templating with Perses interpolation formats. Integrates with prometheus-grafana-engineer for deep PromQL expertise. Use for "perses query", "promql perses", "logql perses", "perses panel query". Do NOT use for datasource configuration (use perses-datasource-manage).
Deploy Perses server: Docker Compose for local dev, Helm chart for K8s, or binary for bare metal. Configure database (file/SQL), auth (native/OIDC/OAuth), plugins, provisioning folders, and frontend settings. Use when user wants to deploy, install, set up, or configure a Perses server instance. Use for "deploy perses", "install perses", "perses setup", "perses server", "run perses". Do NOT use for dashboard creation (use perses-dashboard-create) or plugin development (use perses-plugin-create).
Perses datasource lifecycle management: create, update, delete datasources at global, project, or dashboard scope. Supports Prometheus, Tempo, Loki, Pyroscope, ClickHouse, and VictoriaLogs. Uses MCP tools when available, percli CLI as fallback. Use for "perses datasource", "add datasource", "configure prometheus perses", "perses data source". Do NOT use for dashboard creation (use perses-dashboard-create).
Perses project lifecycle management: create, list, switch, and configure projects. Manage RBAC with roles and role bindings per project. Uses MCP tools when available, percli CLI as fallback. Use for "perses project", "create project", "perses rbac", "perses roles", "perses permissions". Do NOT use for dashboard creation (use perses-dashboard-create).
Perses variable lifecycle management: create Text and List variables at global, project, or dashboard scope. Handle variable chains with dependencies (A depends on B depends on C). Supports 14+ interpolation formats. Uses MCP tools when available, percli CLI as fallback. Use for "perses variable", "dashboard variable", "perses filter", "add variable". Do NOT use for datasource management (use perses-datasource-manage).
Post-mortem diagnostic analysis of failed or stuck workflows. Detects stuck loops, missing artifacts, abandoned work, scope drift, and crash/interruption patterns through git history and plan file analysis. Produces a structured diagnostic report with anomaly confidence levels, root cause hypotheses, and recommended remediation. READ-ONLY: never modifies files. Use for "forensics", "what went wrong", "why did this fail", "stuck loop", "diagnose workflow", "post-mortem", "workflow failure", or "session crashed". Do NOT use for debugging code bugs (use systematic-debugging), reviewing code quality (use systematic-code-review), or fixing issues (forensics only diagnoses).
Review existing Perses dashboards for quality: fetch via MCP or API, analyze panel layout, query efficiency, variable usage, datasource configuration. Generate improvement report. Optional --fix mode. 4-phase pipeline: FETCH, ANALYZE, REPORT, FIX. Use for "review perses dashboard", "audit dashboard", "perses dashboard quality". Do NOT use for creating new dashboards (use perses-dashboard-create).
Check GitHub Actions workflow status after git push using gh CLI. Reports CI status, identifies failing jobs, and suggests local reproduction commands. Use after "git push", when user asks about CI status, workflow failures, or build results. Use for "check CI", "workflow status", "actions failing", or "build broken". Do NOT use for local linting (use code-linting), debugging test failures locally (use systematic-debugging), or setting up new workflows.
Use the `datadog` CLI to manage Datadog resources — monitors, metrics, events, logs, services, errors, and pipelines. Invoke this skill whenever the user asks to query, create, update, or delete Datadog monitors, search logs or errors, check metric values, list APM services, or manage log pipelines. Also trigger when the user mentions Datadog observability tasks like "check the error rate", "look at monitors", "search logs for errors", "list services", or "set up a log pipeline".
A professional guide for handling dynamic deployment parameter configuration (lzc-deploy-params.yml), Go template rendering of manifest files, and front-end page script injection via application.injects for Lazycat MicroServer applications.
Deploys applications to TrueFoundry. Handles single HTTP services, async/queue workers, multi-service projects, and declarative manifest apply. Supports `tfy apply`, `tfy deploy`, docker-compose translation, and CI/CD pipelines. Use when deploying apps, applying manifests, shipping services, or orchestrating multi-service deployments.
Defensive Bash scripting for Linux: safe foundations, argument parsing, production patterns, ShellCheck compliance. Use when writing bash scripts, shell scripts, cron jobs, or CLI tools in bash.