1.1천건 · 관련도순
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 when the user asks about driver fatigue management — circadian rhythm impact on driving, recognizing fatigue, fatigue risk management programs (FRMS), night driving safety, microsleep recognition, drowsiness detection technology, and how HOS rules relate to actual fatigue (and why 11-hour driving is risky even when legal). Reference FMCSA Fatigue Management research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier asks about autonomous trucks — current state of Level 4 development, major programs (Aurora, Kodiak, Plus, Waymo Via, Embark history), regulatory status, operational implications, hub-to-hub model, driver impact, insurance, and what carriers should be doing now (or not doing) to prepare.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "このファイルを変えたら何が壊れる？", "what depends on this function", "影響範囲を調べて", "show me what imports this module", or wants to understand the blast radius before modifying a shared utility, exported type, or public API. Traces import/require references up to two levels deep and lists affected test files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze an idea, proposal, change, claim, or decision from facts through problem, value, mechanism, consequences, evidence, alternatives, and action. Use when the user asks what something is for, why it matters, whether it is worth doing, what impact it has, or how to decide. Do not use for simple factual lookup or straightforward execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive China A-share stock analysis covering fundamental analysis, technical analysis, policy impact assessment, and market-specific features (T+1 trading, price limits, northbound capital flow). Use when user asks about A股分析, Chinese mainland stocks, Shanghai/Shenzhen listed stocks, or needs analysis considering China market characteristics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Captures clause risks, compliance gaps, precedent shifts, contract deviations, regulatory changes, and litigation exposure to enable continuous legal operations improvement. Use when: (1) An unfavorable clause is accepted or slips through review, (2) A compliance deadline is missed or approaching, (3) A new regulation impacts the organization, (4) A contract remains unsigned past SLA, (5) An IP infringement notice is received, (6) New case law changes interpretation in a relevant jurisdiction, (7) A data subject access request reveals process gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify and prioritize risks by impact and controllability. Use for risk management, project planning, and strategic decision support.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Framework-directable information security risk assessment. Identifies threats, evaluates likelihood/impact via a 3x3 matrix, maps findings to any compliance framework, and recommends risk treatment options with prioritization guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Regulatory review across 14 frameworks — compliance review, privacy impact assessment, regulatory gap analysis, data subject rights, consent mechanisms, audit trail, AI ethics review, data flow mapping. Covers GDPR, PIPEDA, HIPAA, PCI-DSS, SOC2, UAE-PDPL, EU AI Act and more.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build accretion/dilution (merger) models in Excel — pro-forma P&L, synergies, financing mix, EPS impact. Pairs with excel-author. Use for M&A pitches, board materials, or deal evaluation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintains library compatibility. Binary/source compat rules, type forwarders, SemVer impact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configures artifacts output layout. UseArtifactsOutput, ArtifactsPath, impact on CI and Docker.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PR test analysis routing. Use for pull request or diff test impact, changed-test review, CI failure interpretation, and focused test matrix recommendations; do not use for general code review or editing tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates changelogs and release notes from git commits, PR titles, and issue references. Organizes changes by impact type (breaking, features, fixes, improvements), formats according to Keep a Changelog standard, and provides version tagging and semantic versioning suggestions. Use when users request "create changelog", "write release notes", "document version changes", or "prepare release".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Arithmetic probes ({{7*7}}→49) confirm the injection point but are not proof of impact. The real goal is OS command execution. Arithmetic detection also fails silently when the app echoes the input back (e.g. inside an HTML attribute like <input value='{{7*7}}'>), producing a false negative even when injection exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows, role/tenant boundary violations, time-of-check vs use, anti-automation defeat, fraud-detection evasion, and subscription/quota abuse. Use when scoping an application after surface-level OWASP Top 10 has been covered, or when the asset is a transactional/marketplace/fintech/e-commerce/SaaS app where logic flaws produce direct financial impact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hunt Open Redirect — all types including low-impact, chained to OAuth token theft → ATO, phishing chains. URL parameter manipulation, JavaScript redirect, meta refresh, header injection. Use when hunting redirect bugs or building ATO chains.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.