747건 · 관련도순
Conservative review of end-user legal exposure from diagnostics targets and probe hosts, by jurisdiction. Use when shipping or editing diagnostics target lists, probe hosts, or bootstrap endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrator context window discipline enforcement. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that waste context, and rationalizing delegation bypasses. Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows. Activates PreToolUse hooks that surface decision points before source file reads and diagnostic command execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs Ansible diagnostic playbooks using ansible-runner and the Ansible Collections ecosystem (ansible.builtin, community.general). Captures system health, service status, and log analysis across inventory hosts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compiler-level code intelligence via native LSP — definitions, references, types, call hierarchies, and diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluating diagnostic tests — sensitivity, specificity, ROC analysis, likelihood ratios, and study design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an Energy Auditor — running a blower-door/duct-leakage diagnostic sequence on a home or light-commercial building, testing combustion appliances for worst-case backdraft risk before recommending air sealing, reconciling utility billing history against walkthrough findings, ranking retrofit measures by savings-to-investment ratio (SIR) for a weatherization or utility rebate program, or writing the prioritized scope of work an install crew executes without the auditor on site. Distinct from an energy-engineer (industrial/commercial capital planning, IPMVP measurement and verification, calibrated simulation) — this role owns the field diagnostics and the residential/light-commercial audit-to-scope handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigates Google Cloud networking issues by analyzing logs, metrics, and diagnostics. Use when investigating VPC Flow Logs (including cost estimation), NAT, firewall, or threat logs, querying latency and throughput metrics, or running Connectivity Tests for path diagnostics. Don't use for generic VM management or non-observability tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adopt declscope on an existing Go codebase and drive its diagnostics to zero. Read this when introducing declscope to a repository, when choosing its configuration, when running declscope shrink for the first time, or when clearing a declscope baseline. Covers sizing each rule before enabling it, reading the diagnostics as structure, the remedy for each shape, and the measurement traps that produce false confidence. For writing new code in a repository that already runs declscope, use declscope-authoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigates Google Cloud networking issues by analyzing logs, metrics, and diagnostics. Use when investigating VPC Flow Logs, NAT, firewall, or threat logs, querying latency and throughput metrics, or running Connectivity Tests for path diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
diagnostic-monitor-read-only-gate
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JIRA-side cache + project-context discovery via the jira-as wrapper. Triggers: 'jira cache status', 'clear jira cache', 'discover project context for PROJ'. Diagnostic-only — no Atlassian state changes. NOT for issue CRUD; NOT for project admin (mk:jira-admin).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "set up my founder social-selling routine", "build a daily engagement block for target accounts", or "turn funding / hiring signals into selling plays"; produces the founder/seller daily operating block — a time-boxed engagement-block spec (substantive value-add comments on target-account posts, never a pitch), warm-touch-before-ask cadence rules, trigger-response plays consuming the social-pulse-monitor B2B trigger watchlist (funding / hiring / launch signals), and a quarterly diagnostic that reads LinkedIn SSI as an input diagnostic only (Estimated, vendor-defined — never a target metric). All volume norms are Estimated/community-derived; all execution is human — zero mass-DM, zero connection-request automation, zero engagement automation (LinkedIn UA §8.2 red line); 1:1 pitch and DM mechanics route to outreach-manager. Not for cold email sequences — use cold-outbound-sequencer. 社交销售/创始人日常互动块/热身触达节奏/触发信号剧本
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with error diagnostics smart debug
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues. Use when the user needs help choosing diagnostic tools, collecting performance data, or understanding tool trade-offs across different environments (Windows/Linux, .NET Framework/modern .NET, container/non-container).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish build performance baselines and apply systematic optimization techniques. Only activate in MSBuild/.NET build context. USE FOR: diagnosing slow builds, establishing before/after measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for optimizing MSBuild incremental builds. Only activate in MSBuild/.NET build context. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs/Outputs on custom targets, volatile properties in output paths (timestamps/GUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, search, target details); falls back to dotnet build /bl, binlog replay with diagnostic verbosity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnostic test / biomarker accuracy — sensitivity, specificity, PPV, NPV, likelihood ratios, accuracy from a 2x2 table; ROC curve, AUC, and the optimal cutoff (Youden) for a continuous biomarker; and post-test probability via Bayes. Use when you have test results vs a gold standard (binary 2x2, or a continuous score + true labels) and need to judge how good the test is, pick a threshold, or compute the probability of disease given a result. Emphasizes the prevalence-dependence of PPV/NPV.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kubb (OpenAPI / Swagger コードジェネレーター) リファレンス。 kubb.config.ts、TypeScript 型・TanStack Query フック・Zod・Faker・MSW モック生成プラグイン、 Fetch / Axios / SWR / React Query クライアント、plugin-client (自前クライアント)。 CLI 8 コマンド、拡張レジストリ (kubb add)、Kubb Studio、Kit (kubb/kit)、 parser-ts / parser-md、adapter-oas、diagnostics、プラグインベース、モノレポ対応。 TanStack Query 本体の API は tanstack-query スキル。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
원격 환경이나 Docker에서 설치, 연동, 실제 사용자 작업을 테스트합니다. 코드 신뢰도에 따른 환경 선택부터 장애 조사와 실행 후 정리까지 다룹니다.