'reliability' 검색 결과

Build Cypress test suites in TypeScript: E2E tests, component tests, custom commands, cy.intercept network control, cy.session login, Cypress Cloud, and CI integration. Covers retry-ability, the command queue, cross-origin flows with cy.origin, and data-driven testing with fixtures. Use when: "write E2E test in Cypress," "Cypress page object / custom command," "cy.," "cy.intercept," "Cypress component test," "Cypress Cloud," "cypress.config.ts." Not for: Playwright suites — use playwright-automation; flaky-test healing or quarantine — use test-reliability; bulk selector regeneration after a UI refactor — use selector-drift-recovery; Selenium-to-Cypress conversion — use test-migration. Related: playwright-automation, ci-cd-integration, visual-testing, unit-testing, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design CI/CD pipelines that run test suites. Covers GitHub Actions and GitLab CI templates, parallelism and sharding, artifact management, flaky-test quarantine, test-result publishing, coverage quality gates, OIDC keyless deploy, and copy-paste workflows for Playwright, Jest, and multi-stage pipelines. Use when: "CI/CD," "GitHub Actions," "pipeline," "test in CI," "GitLab CI," "continuous integration," "test automation pipeline," "shard tests in CI." Not for: per-test flaky healing at runtime — use test-reliability; go/no-go release decisions and smoke-test checklists — use release-readiness; test-result dashboards and trend reporting — use qa-metrics. Related: playwright-automation, qa-metrics, test-reliability, coverage-analysis, release-readiness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Engineering observability and reliability: SLO/SLI design, distributed tracing, alerting, dashboards, capacity planning, toil automation, reliability review. Use for instrumentation or SLO definition.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit a proposed assessment for construct validity, reliability, and alignment to learning objectives. Use when reviewing or quality-assuring assessments before deployment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reliability engineering for cloud systems — SLIs, SLOs, error budgets, SRE practices, runbooks, incident response, on-call rotation, blameless postmortems, chaos engineering, and the NASA Systems Engineering methodology (MCR/SRR/PDR/CDR/ORR phase gates, TAID verification, requirements tracing) adapted to cloud operations. Use when establishing SLOs for a new service, running an incident, writing a runbook, preparing a launch readiness review, or bringing NASA SE discipline to cloud deployments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Specialized hardware interfaces and system reliability for Zephyr RTOS. Covers LVGL GUI development, Audio I2S/Codecs, Watchdog timers, and Fault Injection. Trigger when building human-machine interfaces (HMI), audio devices, or high-reliability mission-critical systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reads model uncertainty from token log-probabilities. Covers collecting logprobs and aggregating multi-token labels, confidence tiers and margins for triage, calibration assessment with ECE, Brier scores, and reliability diagrams against human labels, responsible downstream use of confidence, and reproducibility archives. Use when the user asks about classifier confidence by item, logprobs, top-k tokens, calibration, ECE, Brier, reliability diagrams, or routing low-confidence cases to human review. Codebook and validation design go to text-classification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement circuit breaker logic for agentic tool calls — tracking tool health, transitioning between closed/open/half-open states, reducing task scope when tools fail, routing to alternatives via capability maps, and enforcing failure budgets to prevent error accumulation. Separates orchestration (deciding what to attempt) from execution (calling tools), following the expeditor pattern. Use when building agents that depend on multiple tools with varying reliability, designing fault-tolerant agentic workflows, recovering gracefully from tool outages mid-task, or hardening existing agents against cascading tool failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a task needs the judgment of a DevOps/Site Reliability Engineer — designing deployment pipelines, setting SLOs/error budgets, responding to or reviewing an incident, or making infrastructure/reliability tradeoffs. Distinct from a backend software engineer role — this one owns the system's operational health across all services, not one service's feature code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrates comprehensive production readiness reviews and assessments for GKE clusters and workloads across scalability, security, reliability, observability, backup/DR, and cost optimization. Use when asked to productionize, prepare, assess, audit, or review a GKE cluster or workload before going live to production. Don't use for deep-dive single-domain implementation (use specific domain skills like gke-workload-scaling, gke-platform-security, gke-workload-security, gke-service-networking, gke-reliability instead).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard infrastructure monitoring unrelated to AI agents, or when the agent is not instrumented with OpenTelemetry (for Reliability, Cost, Safety, Security alerts). NOTE: Reliability, Cost, Safety, and Security alerts use generic OTel metrics and work across runtimes (such as Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess the scientific integrity and trustworthiness of publications before relying on their findings. Use this skill whenever evaluating a paper for a workflow, citing a study, building an analysis on published methods, or when a user asks about the reliability of a study. Checks for formal retractions, corrections, expressions of concern, and — critically — informal contradictions where subsequent studies failed to reproduce key findings. Integrates with PubMed, bioRxiv, and Consensus to provide a trust assessment. Use this skill for ANY publication evaluation, retraction checking, author reliability assessment, or when a user says "can I trust this paper", "is this study reliable", "has this been refuted", or "check this publication".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assigns confidence scores to agent outputs based on multiple factors including source quality, consistency, and reasoning depth. Produces calibrated confidence estimates. Activate on 'confidence score', 'how confident', 'certainty level', 'output confidence', 'reliability score'. NOT for validation (use dag-output-validator) or hallucination detection (use dag-hallucination-detector).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when choosing architecture patterns for reliability, performance, messaging, or security in a distributed cloud system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert database administrator specializing in modern cloud databases, automation, and reliability engineering. Masters AWS/Azure/GCP database services, Infrastructure as Code, high availability, disaster recovery, performance optimization, and compliance. Handles multi-cloud strategies, container databases, and cost optimization. Use PROACTIVELY for database architecture, operations, or reliability engineering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

운영 환경에 공개하기 전 품질, 보안, 성능, 사용성을 점검하고 모니터링과 롤백을 준비합니다. 공개 후 확인과 지표에 따른 단계적 배포도 다룹니다.

• 첫 운영 환경 공개 전 준비 확인
• 주요 기능의 단계적 공개 계획
• 모니터링과 공개 후 확인 절차 정리

시스템 장애의 원인, 수정 내용, 재발 방지책을 HTML 슬라이드로 정리합니다. 전용 템플릿으로 발표 구성을 다듬어 기술 담당자와 경영진의 후속 대응 논의를 돕습니다.

• 시스템 장애 회고를 발표합니다
• 결함 원인과 수정 내용을 설명합니다
• 시스템 전반의 개선책을 검토합니다

Build an evaluation process for AI agents using success, reliability, cost, and latency measures. Define scoring criteria, repeatable environments, failure analysis, and regression tests that check for recurring problems to support model selection and system improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building an initial agent evaluation process
• Comparing models on actual work tasks
• Investigating a drop in evaluation scores

Design AI agents that break down goals, plan actions, use tools, and correct their own mistakes. The guidance focuses on reliable execution, clear operating boundaries, and managing conversation context as tasks grow longer.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing an agent's planning and execution loop
• Breaking a complex goal into manageable tasks
• Reviewing self-correction and reliability patterns