'diagnose' 검색 결과

Diagnose GKE TPU slice creation failures caused by shared nodes. Check slice status, partition labels, and monitoring data to identify conflicting resource groups, then provide resolution steps for the user to apply.

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

• Investigating node overlap behind SliceCreationFailed
• Finding slices that share nodes across partition shapes
• Checking whether resource conflicts existed at incident time

Diagnose GKE TPU node pool creation or expansion failures despite reserved capacity. Trace which virtual machines and unhealthy node pools occupy reservation slots, check automatic repair settings, and provide remediation steps for the user to apply.

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

• Investigate TPU capacity errors despite a reservation
• Identify node pools occupying reserved TPU capacity
• Check automatic repair settings on unhealthy TPU nodes

Diagnose GKE TPU slice creation failures and pending JobSets caused by unstable managed instance groups, the underlying VM groups. Read-only checks examine logs, instance status, upgrades, and repairs to identify causes and suggest user-applied fixes.

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

• Investigating TPU SliceCreationFailed errors
• Checking whether pending JobSets relate to MIG instability
• Tracing stalled node pool upgrades or repairs

Diagnose GKE TPU virtual machines that remain in repair by checking instance status, host events, and automatic repair history. Understand the impact on grouped TPU nodes and identify recovery steps for the user to apply.

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

• Investigating TPU VMs that remain in REPAIRING
• Assessing how a failed node affects a TPU slice
• Checking automatic repair history and failure reasons

Diagnose Google Cloud Filestore mount failures by checking client access rules, network firewalls, and audit logs. Distinguish permission errors from connection timeouts, then provide a structured report and remediation commands that require confirmation before execution.

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

• Investigating a Filestore mount that hangs or fails
• Diagnosing access-denied errors from a GKE workload
• Checking client permissions and VPC firewall rules

Diagnose GKE nodes marked NotReady or Unknown using node conditions, events, logs, and resource metrics. The skill gathers evidence, distinguishes temporary transitions from faults, and proposes fixes for a person to apply.

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

• Investigate persistent NotReady or Unknown node status
• Check why kubelet stopped reporting node status
• Investigate evictions or Pending Pods linked to node health

Diagnose failures in GKE HorizontalPodAutoscaler (HPA), which adjusts Pod counts automatically. Investigate missing metrics, unexpected scaling behavior, and slow reactions, then receive proposed configuration fixes or commands for review before deployment.

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

• Investigating unknown metrics and HPA errors
• Diagnosing workloads that will not scale up or down
• Troubleshooting scaling to and from zero

Diagnose interrupted or repeatedly restarting AI training jobs managed by JobSet on GKE. Correlate restart metrics, node events, host health, and worker logs to distinguish Spot VM preemptions, infrastructure failures, and application crashes, then recommend responses.

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

• Investigating repeated JobSet restarts
• Checking whether Spot VM preemptions interrupted training
• Tracing recurring failures to a physical host

Diagnose declines in Google Ads conversions, conversion value, and leads by comparing periods, traffic, device breakdowns, impression share, and account changes. Use live account data through the Google Ads MCP Server or receive queries and diagnostic guidance for manual execution.

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

• Investigate sudden drops in conversions or conversion value
• Identify budget or ad rank limits on impression share
• Separate traffic declines from conversion rate declines

Configure Google Cloud logs across multiple projects, either by storing them centrally or querying them together where they already reside. The skill guides routing, access permissions, and log views, and helps diagnose missing logs and permission failures.

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

• Collect logs from multiple projects in one central bucket
• Query distributed logs without copying their data
• Set log access boundaries by project or log type

Diagnose failed model requests from OpenShell sandboxes to hosted APIs or local servers such as Ollama and vLLM. Check provider attachment, access rules, credentials, network layout, and client settings to identify the narrowest configuration change needed.

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

• Diagnose failed requests to hosted model APIs
• Troubleshoot connections to Ollama or LM Studio
• Investigate credential and endpoint mismatch errors

Find and call tools in connected services such as Linear and GitHub through superset mcp. This skill also helps diagnose connection and permission errors and access tools missing from an agent’s own tool list.

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

• Check which tools a connected service offers
• Create a Linear issue through a connected account
• Diagnose authentication and permission errors

Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.

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

• Investigating failed PR checks
• Separating intermittent test failures from code defects
• Checking whether the base branch already fails

Diagnose Superset connection, host, terminal, authentication, and update problems using status checks and logs. Get a matching fix, approve changes before they run, and verify whether the original problem is resolved.

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

• Investigating a Superset connection failure
• Recovering an offline host
• Checking terminal attachment problems

Diagnose unexpected terminal-tools results, including empty output, missing exit codes, expired output handles, and busy sessions. Use returned status fields to distinguish ongoing work, output limits, shell behavior, and failures, then choose a recovery step.

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

• Investigate empty or truncated command output
• Interpret missing exit codes and conflicting status fields
• Resolve job limits and busy terminal sessions

Check implemented features through conversational acceptance testing, confirming behavior from the user's perspective. Record each result, retain testing progress, and diagnose reported problems to prepare verified repair plans for a subsequent execution step.

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

• Check completed features from a user's perspective
• Resume an unfinished acceptance testing session
• Diagnose issues and prepare repair plans

Investigate errors and unexpected behavior through reproduction, isolation, diagnosis, and a proposed fix. Receive a structured report covering the root cause, necessary code or configuration changes, and suggested tests to prevent the issue from returning.

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

• Investigate an error message or stack trace
• Diagnose behavior that differs between staging and production
• Trace a failure that appeared after deployment

Diagnose paid advertising performance using account evidence, financial constraints, and experiments. Draft ranked changes to budgets, bids, or ad delivery, and apply supported operations only after approval and state checks, retaining a way to reverse them.

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

• Reviewing budget allocation and bids
• Planning ad pauses and creative rotation
• Assessing search terms before adding negative keywords

Diagnose file access problems by checking whether the target directory exists, inspecting its contents, and reviewing access permissions. The workflow guides path or permission fixes, then retries the original file operation or script.

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

• Investigating file access failures
• Checking paths when a script fails
• Creating a missing directory

Diagnose file access problems by checking directories, permissions, file headers, and line counts in parallel batches. Also reviews TypeScript imports, fixes duplicates and type-only imports, and checks module exports before retrying the failed operation.

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

• Investigate missing files, incorrect paths, and permission errors
• Review multiple source files in parallel batches
• Check CSS and configuration file headers and line counts

Turn unstructured clinical encounter summaries into SOAP notes, a four-part format for medical records. Organize symptoms and findings, include diagnoses with ICD-10 classification codes, and document treatment steps, follow-up timing, and reasons to return for care.

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

• Converting unstructured clinical summaries into SOAP notes
• Documenting diagnoses with ICD-10 codes and supporting reasoning
• Organizing treatment details, dosages, and timelines

Diagnose Claude in Chrome connection failures on macOS by checking native messaging hosts, the processes linking Chrome to Claude, and their settings. It guides fixes for competing configurations, stale wrappers, and session conflicts, including restart steps.

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

• Investigate a browser extension connection error
• Restore browser integration after a Claude Code update
• Switch browser automation between Claude Code and Cowork

Diagnose why an AI workflow becomes inconsistent despite receiving extensive information. Through guided questions, define what to retain, retrieve when needed, or exclude, and develop a memory structure and a research-to-implementation process with focused context.

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

• Diagnosing vague answers despite extensive input
• Defining information boundaries between agents
• Planning persistent memory and on-demand retrieval

Diagnose failed GitHub Actions runs using available job and step evidence. Identify the likely cause, propose a focused fix, and, when implementation is requested, update local code and run relevant checks while noting what needs remote verification.

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

• Investigate a failed GitHub Actions run
• Find failing checks associated with a pull request
• Implement and locally check a focused fix