Analyze latest policy analysis sweep runs (*_policy_analysis_*) by comparing episodes/summary metrics, diagnostics, and video artifacts; generate a concise markdown report and optional frame snapshots.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
433건 · 관련도순
Analyze latest policy analysis sweep runs (*_policy_analysis_*) by comparing episodes/summary metrics, diagnostics, and video artifacts; generate a concise markdown report and optional frame snapshots.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Regression analysis, ANOVA, generalized linear models, Bayesian methods, and model selection. Covers the full modeling workflow from problem formulation through diagnostics -- linear regression, logistic regression, Poisson regression, mixed-effects models, prior specification, posterior inference, AIC/BIC comparison, cross-validation for model selection, and assumption checking. Use when fitting models, testing hypotheses, or selecting among competing statistical explanations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenStack networking debug operations skill for SDN troubleshooting, packet tracing, and flow analysis. Covers OVS/OVN debugging (ovs-vsctl, ovs-ofctl, ovs-appctl, ovn-nbctl, ovn-sbctl, ovn-trace), security group analysis via OVS flow rules and conntrack, DHCP troubleshooting through namespace inspection and dnsmasq diagnostics, floating IP diagnosis with NAT rule and ARP verification, network namespace inspection (ip netns), MTU chain analysis for overlay networks, DNS resolution debugging, and east-west traffic diagnosis. Use when diagnosing network connectivity failures, tracing packets through the SDN stack, or analyzing flow tables in a running OpenStack cloud.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Essential Zephyr RTOS kernel services. Covers thread lifecycle and priority, the logging subsystem for diagnostics, and the interactive shell for real-time hardware inspection and debugging. Trigger when writing application flows, adding logging to modules, or creating interactive CLI commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design, estimation, measurement error, external validity, and interpretation. Use when checking whether a conjoint design or analysis holds up, or answering referee comments on one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a raw Qualtrics conjoint export into an analysis-ready long-format dataset, covering export settings, identifying the implementation, package or manual wide-to-long reshaping, choice-profile alignment, ratings, reference categories, pilot exclusion, and subgroup merges. Use when the user has a conjoint CSV to clean, reshape, or debug, cannot align choices with profiles, or asks what the data must look like before AMCE estimation. Design goes to conjoint-design, validity review to conjoint-diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs conjoint and factorial-vignette experiments, covering attribute architecture and randomization restrictions, effective-N power, treatment realism, the choice among AMCE, marginal-mean, and AMIE estimands, forced-choice versus rating designs, and PAP tiers. Use when the user is planning a conjoint, drafting or critiquing an attribute table, asking how many respondents or tasks are needed, whether to report AMCEs or marginal means, or how to test interactions. Reviewing an existing design goes to conjoint-diagnostics, cleaning the export to conjoint-cleaning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design integrity, estimation, measurement error, external validity, and interpretation, including the guardrail against reading an AMCE as majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation or interpretation. New designs go to conjoint-design, reshaping to conjoint-cleaning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when claiming the AI bounty on the tDVV mainnet sidechain. This public claim skill now supports Portkey AA/CA only, requires CA sync and holder preflight before any write, and routes to AA/CA onboarding, AA/CA claim, or diagnostics-only stop handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review pytest test effectiveness against authoritative contracts, relevant faults, behavior-preserving refactors, realistic boundaries, isolation, and diagnostics. Use for test-quality audits, coverage-gap reviews, regression-test changes, or mocking reviews; preserve existing project gates rather than inventing coverage targets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discover and run configured quality gates for requested or changed work, preserve diagnostics as evidence, route failures to the appropriate causal/domain capability, and verify corrections. Use for linting, formatting, type-checking, configured hook checks, or pre-completion quality verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies. Covers single-stock diagnostics and batch screening for both Graham cigar-butt and Buffett quality-compounder criteria. Runs cross-statement reconciliation before scoring. Data from Longbridge CLI first, MCP fallback, WebSearch only for genuine gaps. Triggers: "格雷厄姆", "巴菲特", "捡烟蒂", "烟蒂股", "NCAV", "净流动资产", "护城河", "价值投资", "安全边际", "深度价值", "撿煙蒂", "煙蒂股", "淨流動資產", "護城河", "安全邊際", "Graham", "Buffett", "cigar butt", "net-net", "NCAV screen", "moat", "value investing", "margin of safety", "deep value", "quality compounder", "價值投資", "深度價值", "防御型投资者", "防禦型投資者"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Alibaba Cloud Elastic Compute Service (ECS) using the @alicloud/ecs20140526 TypeScript SDK. Use when working with cloud servers on Alibaba Cloud, including instance lifecycle (create, start, stop, reboot, delete), disks and snapshots, images, security groups, VPC networking, EIP, ENI, SSH key pairs, dedicated hosts, auto provisioning, launch templates, Cloud Assistant commands, tags, system events, diagnostics, storage capacity units, and prefix lists. Covers all 374 APIs of the ECS 20140526 version.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Super-skill for developing Haskell projects with cabal nix-style builds. Orchestrates HLS diagnostics, Haddock, Hoogle, source formatting, and cabal-gild into one workflow. Use when writing, editing, refactoring, building, typechecking, fixing compiler errors, renaming symbols, looking up APIs, or changing dependencies in Haskell projects. Treat cabal.project as the source of truth, prefer HLS before full builds, and prefer local docs over remote lookup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Executes automated diagnostics using the AWS Systems Manager Automation API and SSM Documents. Collects system metrics via the CloudWatch GetMetricData API and correlates with AWS Health events.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses failed AWS CloudFormation stack operations using the AWS CLI (aws cloudformation describe-stack-events) and cfn-lint validator. Traces resource creation failures, rollback causes, and nested stack dependency chains.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Executes Ansible playbooks for server diagnostics and remediation using ansible-runner Python SDK. Supports inventory parsing, vault-encrypted credentials, and real-time task output streaming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic debugging methods, log analysis, and performance diagnostics. Use when debugging issues, analyzing errors, or troubleshooting incidents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a C or C++ build uses GCC and needs build-mode flags, warning triage, debug info, LTO, PGO, or a compilation error explained. Not for Clang-only diagnostics: use clang.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a C or C++ build uses clang and needs diagnostics, optimization remarks, clang-tidy, ThinLTO with lld, LLVM PGO, or a GCC-to-Clang migration. Not for LLVM IR work: use llvm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user needs official desktop Obsidian CLI Bases or Bookmarks workflows, including base discovery, view/query operations, base item creation, and bookmark management. Keep this skill separate from general note CRUD, runtime admin, Sync/Publish, and devtools diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user wants local Obsidian note or metadata work done primarily through documented official desktop `obsidian` CLI commands, with limited local vault filesystem support when needed for parent folders, path checks, ambiguity resolution, verification, or safe vault structure operations. Best for local vault search, note reads, exact-path note updates, backlinks, tasks, properties, templates, and local history. Do not use it for runtime admin, devtools diagnostics, workspace/navigation administration, community tools, `obsidian://` launcher tasks, Headless Sync or Publish workflows, or plugin-specific APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.