'risk' 검색 결과

Runs cis-pQTL Mendelian randomization for drug-target validation using UKB-PPP (Olink), deCODE (SomaScan), Fenland, INTERVAL, ARIC, and FinnGen-PPP proteomes plus colocalization triangulation, phenome-wide on-target adverse-effect scans, cross-platform Olink/SomaScan replication, and PAV (protein-altering variant) sensitivity. Use when nominating or de-risking a drug target from plasma-proteome GWAS, mimicking pharmacological inhibition via cis-pQTL instruments, separating shared-causal from LD-confounded signal under the Schmidt 2020 cis-MR framework, screening on-target adverse phenotypes pheWAS-style, or producing publication-grade STROBE-MR plus PP.H4 evidence for a target gene.

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

Use this skill when the user asks about the financial differences between being an owner-operator vs company driver — gross pay, expenses, net pay, capital requirements, risk tolerance, lifestyle, and how to evaluate the path. Reference industry pay surveys.

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

Use when a driver or carrier asks about trucker mental health — depression, isolation, stress, fatigue, suicide risk, addiction, EAP programs, or wellness benefits. Covers evidence-based programs, hotlines, carrier-side EAP design, and how mental health affects safety and retention.

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

Use when a carrier asks whether to buy or lease their next tractor (or trailer), comparing full-service lease (Ryder, Penske, NationaLease), capital lease, finance lease, walk-away open-end lease, or cash purchase. Covers tax treatment, residual risk, maintenance bundling, balance-sheet impact, and cash-flow modeling.

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

Use this skill to understand FMCSA cardiac certification standards. Covers what cardiac conditions disqualify, time-to-clearance, and what documentation is needed for examiner certification.

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

Use when a driver has been disqualified or is at risk of disqualification — major offense convictions (DUI, leaving the scene, drug trafficking with CMV), serious traffic violations, RR-grade-crossing violations, imminent-hazard out-of-service, or Clearinghouse positive-test prohibited status. Also use when planning a return-to-duty pathway, SAP process, or reinstatement timeline. Covers 49 CFR 383.51, Part 40 Subpart O, and Part 391.15.

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

Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.

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

Use this skill when the user asks about cybersecurity for a trucking carrier — protecting ELD data, customer information, financial systems, EDI integrations, fleet telematics, ransomware risk, vendor / shipper data sharing, incident response, and FMCSA cyber-recommendations. Reference NIST + CISA cybersecurity frameworks.

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

Threat-models protocols where authority, scarce resources, bonds, bounties, escrow, reputation, ordering, adjudication, or settlement create strategic incentives. Use to test attack utility, conservation, collusion, Sybil resistance, oracle capture, griefing, custody, liquidity, and residual risk. NOT for choosing payment or bond amounts without evidence, smart-contract code audit, legal or employment classification, DeFi trading, admitting workers, or settling claims.

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

Handle mental health crisis situations in AI coaching safely. Use when implementing crisis detection, safety protocols, emergency escalation, or suicide prevention features. Activates for crisis keywords, safety planning, hotline integration, and risk assessment.

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

Plan, evaluate, and adopt agent infrastructure for a named workload. Use for agent runtime/framework selection, agent evaluation or observability plans, memory and tool boundaries, infrastructure cost controls, and organizational adoption. Covers workload-first comparison, risk and recovery planning, held-out evaluation, cost accounting, and staged rollout. Not a vendor ranking or a production certification. NOT for implementing a specific agent behavior (agentic-patterns), building a specific agent (ai-engineer), prompt optimization (prompt-engineer), or conventional ETL workflow design (jury_rig-architect).

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

Audit a compliance-ladder design (C0-C6) and transcript-fidelity ladder (T0-T5) plus their adapter conformance fixtures — Codex, Claude Code, Cloudflare, Ollama/LM Studio, custom stdio/HTTP agents — for the two failure modes that make a C-badge or T-fidelity label a lie: the ladder disagreeing with itself across doc/schema/ui/probe surfaces, and a level being reachable by self-report because no daemon-witnessed negative probe actually tries to forge it. Use when designing or freezing a compliance ladder, wiring an adapter conformance probe suite, deciding whether a numeric C-badge or T-label is safe to ship, or investigating a self-attestation or observed-to-controlled bypass risk. NOT for auditing a cryptographic protocol or whitepaper for adversarial soundness (`redteam-review`), writing TLA+/formal invariants for a daemon monitor (`runtime-verification-for-agents`), or agent identity, successor linkage, and reputation across restarts (`agent-identity-continuity-reputation`).

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

Audit an existing Coval evaluation setup for coverage, misleading scores, missing evidence, judge validation and execution risk. Read-only; use when inheriting an eval or deciding whether its results support a release decision.

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

Consult Claude Code from Codex for a second opinion while Codex remains responsible for implementation and verification. Use when the user asks Codex to collaborate with Claude, consult Claude, ask Claude for a plan, get a Claude review, delegate analysis to Claude, or says "Claudeと一緒に", "Claudeに相談", "Claudeにレビューしてもらう", "Claudeの意見も聞く", or "Claudeと計画を立てる". Also use when an explicit independent planning or review pass from Claude would materially reduce risk on a complex coding task.

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

This skill should be used when the user wants to "stress-test a design", "challenge an idea", "red team a proposal", "get critical feedback on a design", "validate a design", "adversarial architecture review", "risk assessment", "設計を検証して", "反論をもらいたい", "設計を批判的にレビュー", "デビルズアドボケート", "ストレステスト", "弱点を指摘して", "穴を見つけて", "この設計で良いか", "リスク評価", "設計のアーキテクチャレビュー", or mentions structured adversarial review of a proposal or design. NOTE: Use this for validating PROPOSALS and DESIGNS through adversarial debate, NOT for generic code review, PR review, or normal review requests (use /codex:review or /codex:adversarial-review for those). Also NOT for investigating unknown bugs (use /agent-dialectics:strong-inference for that).

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

Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.

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

Set up, resume or troubleshoot cmail custom-domain email (domain at any registrar → Cloudflare Email Routing → any inbox; optional GoDaddy automation and Gmail send-as): runs cmail setup itself, asking only for missing input, secrets or risky approvals. Don't use for mail migrations or campaigns.

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

[40] PLAN. Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on "plan this", "how should we approach", "what's the strategy", "steps to complete", or when facing complex multi-step work.

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

[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.

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

[62] VALIDATE. Final self-check before delivery. Verify goal alignment, completeness, correctness, and identify residual risks. Produces quality score (0-100) and delivery status. Use when completing any significant work, before handoff, or when you need confidence that work is ready.

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

[02] META. Create new skills when existing ones don't cover the task. Analyze unique requirements, build framework (Frame → Research → Plan → Execute), integrate risks, and declare new skill. Use when facing novel problems that existing skills can't address.

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

Scan your Claude Code configuration (.claude/ directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.

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

Expert security auditor for AI Skills and Bundles. Performs non-intrusive static analysis to identify malicious patterns, data leaks, system stability risks, and obfuscated payloads across Windows, macOS, Linux/Unix, and Mobile (Android/iOS).

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

Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.

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