29건 · 관련도순
Diagnoses applications that fail to start or repeatedly crash on GKE, Google's managed Kubernetes service. It examines logs, events, memory use, image pulls, and connectivity, then proposes configuration patches or commands without applying live changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Transmit and capture RF waveforms using Wireless Testbench with NI USRP radios (X410, X310, N310, N320, N321, N300, X300, E320). Use when generating test signals, transmitting over the air, capturing IQ data, performing loopback tests, configuring multi-antenna setups, or troubleshooting dropped samples and gain settings. Covers basebandTransceiver, basebandTransmitter, basebandReceiver, continuous and once transmit modes, foreground and background capture, and UseRadioBuffer options. Also use when the user mentions transmit waveform, capture signal, IQ data, loopback, RF gain, sample rate, or antenna configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement Purpose-Based Access Control (PBAC) architecture including purpose ontology definition, policy engine configuration, audit logging of purpose verification at query time, and integration with existing IAM systems. Enforces GDPR Article 5(1)(b) purpose limitation technically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
One-shot perspective reset that surfaces blind spots mid-work. Scans what the user has been doing, generates one abstract reframing question, and runs 3 quick checks (scope drift, side effects, better approach) in under 10 lines. No dialogue, no code. Trigger phrases: "/stepback", "step back", "한발 물러서", "넓은 관점", "놓치는 거 없나", "방향 맞나", "zoom out", "큰 그림", "방향이 맞는 거야", "잠깐 멈춰", "지금 뭘 하고 있는 거야", "blind spot", "재확인"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kubernetes 설정 파일 작성과 검토, 장애 원인 조사를 돕습니다. 상태 확인, 권한, 리소스 제한, 자동 확장 설정 예시와 조사 명령을 참고할 수 있습니다.
Create and validate Terraform alerts for GKE using PromQL, a monitoring query language. Cover response times, errors, traffic, memory usage, and cluster health, with checks for alert timing, duplicate signals, and metric ingestion costs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps deploy, manage, and troubleshoot applications on Kubernetes using kubectl and Helm. Covers container logs, resource settings, network access, and deployment strategies to investigate failures and review how applications run.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit paid-ad landing pages for message consistency, mobile usability, accessibility, performance, forms, consent, tracking, and destination safety. Get evidence-based findings and recommendations ready for experiments to address obstacles to completing the intended action.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Help a spawned worker check which date-range helpers and external integrations are available and how to call them. The catalog explains environment settings, local broker access, and availability checks so the worker can choose tools for its task.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Running an in-bundle DOCA service as a container on a BlueField (Argus, DMS, Firefly, or UROM service): kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness. Trigger on "how do I run my built service on the BlueField?", "where do I drop the pod-spec YAML?", "pod stuck in Pending / ImagePullBackOff / CrashLoopBackOff", "container Running but service isn't ready", "pod restart-loops after edit", or "DMS and Firefly together", even without naming container deployment. A DOCA-linked binary launched directly on the host or Arm belongs to doca-bare-metal-deployment. Covers smoke-before-bulk and the layered error taxonomy (pod-spec, scheduling, image pull, runtime, mount, network, version, host). Refuse and route elsewhere for per-service config schemas, DOCA install, library-API questions, external NVIDIA services (BlueMan, HBN, SNAP, Virtio-net), or full Kubernetes-cluster ops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or InsufficientVCPUQuota, upgrade stuck, spot or zone disruption, a bare VMExtensionProvisioningError or AllocationFailed wrapper, an uncataloged capacity symptom, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues (use aks-gpu-inference); cluster creation or provisioning (use azure-kubernetes); cost (use cost-analysis from the optional azure-cost plugin); pod rightsizing (use azure-kubernetes); a fully qualified documented AKS signature with every required nested qualifier (use aks-known-issues); standalone failures on non-AKS Azure resources (use azure-diagnostics). Unqualified errors and open-ended incidents stay here only for AKS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grida AI agent system work: `@grida/daemon` (DaemonServer, loopback HTTP perimeter, files/workspaces, secrets store, daemon discovery) and `@grida/agent` (the agent tenant: sessions, providers/BYOK, runtime/tool execution, skills discovery, prompts, tiers, sandbox hosts). Use for `packages/grida-daemon/**`, `packages/grida-ai-agent/**`, desktop sidecar protocol changes, agent chat transport, and bugs in agent state or streams. For pure Electron window, preload, menu, deep-link, or CDP work, use `desktop`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build safe, local, defensive reproductions of ALREADY-PATCHED, publicly disclosed security vulnerabilities (CVEs, vendor advisories, AI-agent incidents) for whitepapers, control testing, and education. Use this skill whenever the user wants to reproduce, demonstrate, or write up a known vulnerability or security incident — phrases like "reproduce this CVE", "build a repro for", "demonstrate the EchoLeak/Cursor/postmark-mcp issue", "show how this exploit worked", "add a reproducibility guide", or "pull the NVD/CVE details for". It fetches advisory metadata from NVD and CVE.org, confirms the issue is fixed, and produces a vulnerable-vs-patched harness that is offline, loopback-only, and uses synthetic markers. It NEVER discovers, develops, or weaponizes new zero-days and refuses any unpatched or live-target request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or InsufficientVCPUQuota, upgrade stuck, spot or zone disruption, a bare VMExtensionProvisioningError or AllocationFailed wrapper, an uncataloged capacity symptom, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues (use aks-gpu-inference); cluster creation or provisioning (use azure-kubernetes); cost (use cost-analysis from the optional azure-cost plugin); pod rightsizing (use azure-kubernetes); a fully qualified documented AKS signature with every required nested qualifier (use aks-known-issues); standalone failures on non-AKS Azure resources (use azure-diagnostics). Unqualified errors and open-ended incidents stay here only for AKS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose NCCL failures and adjacent training-pod failures on HyperPod GPU clusters (EKS or Slurm) — training hangs, AllReduce / collective-op timeouts, EFA or libfabric errors, rendezvous failures, EFA TCP fallback, /dev/shm or memlock issues, NCCL version mismatch across pods, container OOM / exit-137 / OOMKilled, GPU OOM (CUDA out of memory), CrashLoopBackOff / Pending pods, MASTER_ADDR DNS, NetworkPolicy blocking. Not for single-node hardware faults (→ hyperpod-node-debugger § G) or cluster-creation EFA / SSM failures (→ hyperpod-cluster-debugger § A / § F).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose and fix Kubernetes pods, CrashLoopBackOff, Pending, DNS, networking, storage, and rollout failures with kubectl.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix Gorse recommendation engine pods crashing with "user: unknown userid 65532" error. Use when: (1) Gorse master/server/worker pods show CrashLoopBackOff or Error status, (2) Logs show "failed to get user directory" with unknown userid, (3) Running gorse containers with runAsNonRoot security context and custom UID. The gorse images call os.UserHomeDir() at startup which requires the UID to exist in /etc/passwd.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked navigation, or requests involving private, loopback, link-local, or metadata IP destinations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
World-class Kubernetes operations - deployments, debugging, Helm charts, and the battle scars from managing clusters that serve millions of requestsUse when "kubernetes, k8s, kubectl, helm, pod, deployment, service, ingress, configmap, secret, statefulset, daemonset, hpa, pvc, crashloopbackoff, imagepullbackoff, oomkilled, liveness probe, readiness probe, kubernetes, k8s, containers, docker, helm, deployment, devops, cloud-native" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the diff adds or changes a loopback HTTP or WebSocket server, a bind address, a Unix socket, named pipe, XPC or D-Bus service, an Electron or Tauri main-process handler, a custom URL scheme or file association, a privileged helper or updater, or code that spawns tools inside directories a user or download supplied
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you draw a screen as HTML mockup documents (one per variant) - the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task is in pm_uat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to human_uat or need_revision
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate MaaFramework Pipeline nodes and recognition snippets from screenshots or observed UI state. Use for OCR node generation, ROI sweep, choosing TemplateMatch/OCR/ColorMatch/CustomRecognition, preserving target-file schema style, and designing `next`/`[JumpBack]` links before merging generated nodes into pipeline JSON.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Kubernetes pod and node logs to find the root cause of crashes, restarts, and OOM kills. Use when the user shares kubectl logs, describes CrashLoopBackOff or Pending pods, or asks why a deployment is unhealthy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.