Loading...
Loading...
Found 163 Skills
Use when user asks about 2 Privatrecht, Private Law, ZGB, OR, Zivilgesetzbuch, Obligationenrecht, civil code, contract law, Privatrecht, Handelsrecht, commercial law, SR 2xx. Covers SR category 2 of the Systematische Rechtssammlung.
Use when selecting, installing, configuring, smoke-testing, documenting, or troubleshooting MCP servers for academic search, arXiv, Semantic Scholar, OpenAlex, Crossref, PubMed, Zotero, Overleaf, Google Scholar, paper metadata, or scholarly source tooling.
Track AI engine brand narratives. Use when: detecting narrative drift, misrepresentation, or competitor narrative gains over time.
Safe-release techniques DURING rollout: feature flags, progressive rollouts, canary analysis, guardrail metrics, production smoke tests, and synthetic users. Bridges QA and SRE practices. Use when: "feature flag testing," "canary deploy," "progressive rollout," "guardrail metrics," "dark launch," "safe rollout." Not for: scheduled probes that run continuously after release — use `synthetic-monitoring`. Not for: designing tests from prod telemetry — use `observability-driven-testing`. Related: release-readiness, synthetic-monitoring, observability-driven-testing, qa-metrics.
Scheduled probes that run CONTINUOUSLY after release. Covers probe design for critical user journeys, alerting integration, SLA validation, multi-region monitoring, and the boundary between QA and SRE. Use when: "synthetic monitoring," "uptime testing," "scheduled probes," "SLA validation," "availability monitoring," "post-deploy checks." Not for: safe-release techniques during rollout — use testing-in-production. Not for: designing tests from prod telemetry — use observability-driven-testing. Not for: a one-shot post-deploy smoke gate tied to a release — use release-readiness. Related: testing-in-production, release-readiness, performance-testing, qa-metrics.
The user corrected an answer about a video — "no, it actually says X", "that's the wrong timestamp", "you misread the error code" — or asks why a video answer was wrong. Use this to record the correction as a lesson so future answers on similar questions improve, and to show what the system has learned and saved.
Senior Site Reliability Engineer & Debug Architect. Expert in AI-assisted observability, distributed tracing, and autonomous incident remediation in 2026.
Execute Instantly incident response procedures with triage, mitigation, and postmortem. Use when responding to Instantly-related outages, investigating errors, or running post-incident reviews for Instantly integration failures. Trigger with phrases like "instantly incident", "instantly outage", "instantly down", "instantly on-call", "instantly emergency", "instantly broken".
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
Injects managed chaos into environments to test system resilience. Validates that self-healing and monitoring systems work as expected under stress.
Create a blameless postmortem when the user asks to write a postmortem, document what went wrong, analyze an incident, or run a 5 Whys analysis
Use when working with incident response incident response