'authority' 검색 결과

Apply the aoa-safe-infra-change workflow inside an abyss-* repository using repo-relative operational surfaces, explicit local authority notes, rollback posture, and local validation commands. Use when the base infra-change workflow is correct but a thin project overlay is needed for one abyss repo. Do not use when the base skill is sufficient without local adaptation or when the task is really about producing a shareable artifact.

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

Comprehensive backlink analysis using DataForSEO API. Analyze backlink profiles, find link building opportunities, detect toxic links, compare with competitors, and identify link gaps. Use when user says "backlinks", "link building", "referring domains", "link profile", "toxic links", "link gap", "competitor links", or "domain authority".

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

Content quality audit for both traditional SEO (E-E-A-T) and AI search (citability, structure, authority). Use when user says "content audit", "content quality", "E-E-A-T", "AI citability", "content analysis", or "is my content good for SEO".

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

Reconcile SDD Composy task Markdown and the JSON projection: read-only inspect and plan, then apply only with an explicit authority and the CONFIRM-SDD-SYNC token. Use when task contracts and operational state diverged — 'sincronizar as tarefas', 'o JSON das tasks está desatualizado', 'markdown and json disagree'. Do NOT use to list or advance tasks (sdd-tasks), for a status overview (sdd-status), or to simulate approval.

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

Use this skill when the user asks about towing + recovery operations — separate FMCSA authority class, light-duty vs medium-duty vs heavy-duty wrecker rules, AAA + AAA-Plus contracts, Roadside-Assistance (RA) operations, "non-consensual tow" rules + state-by-state, and how towing operations differ from general freight. Reference state Public Utility Commission + 49 CFR 395 application.

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

Use this skill when the user asks specifically about preparing for the New Entrant Safety Audit (NESA) under 49 CFR 385 Subpart D — different from a Compliance Review. Covers what auditors look at, the 18-month window, automatic failure conditions, the 60-day fix window, what to NOT do, and how to convert from "new entrant" to permanent authority. Cite 49 CFR 385.301-321.

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

Use this skill to understand the value and limits of CVSA decals. Covers when they apply, what they signal, and inspector discretion.

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

Use this skill when the user asks about US-Mexico cross-border CMV operations — long-haul cross-border program, B-1 visas for Mexican drivers, FMCSA OP-1(MX) authority, US-Mexico border commercial zones, USMCA / NAFTA implications, customs brokerage (C-TPAT, FAST), and how a US carrier handles cross-border loads. Reference 49 CFR 365.501-507.

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

Use this skill when the user asks about Household Goods (HHG) movers — 49 CFR 375 + 376 consumer protection rules, FMCSA HHG-specific authority, mover certification, binding vs non-binding estimates, dispute resolution, weight ticket requirements, valuation coverage, and how HHG operations differ from general freight. Cite 49 CFR 375.

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

Use this skill to set proper expectations on how a DataQ challenge is actually reviewed. Covers state vs federal authority, typical timelines, and common review outcomes.

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

Use this skill when an owner-operator (single CDL driver, single operating authority) needs to comply with random testing. Covers consortium membership, pool size requirements, and self-employed driver rules.

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

Use this skill when the user asks anything that touches US Department of Transportation (DOT) or Federal Motor Carrier Safety Administration (FMCSA) regulation for commercial motor vehicles (CMVs) — including who's regulated, MC vs DOT number differences, operating authority, BOC-3 process agents, MCS-150 biennial updates, intrastate vs interstate distinctions, exemptions, or pointing to the right CFR section. Cite the actual regulation when answering. Don't guess; if you're not sure which Part applies, ask the user to clarify the operation type (for-hire vs private, passenger vs property, intra vs interstate, hazmat, gross weight rating).

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

Use this skill when the user asks about US-Canada cross-border CMV operations — CVOR (Commercial Vehicle Operator's Registration), NSC (National Safety Code), Ontario / Quebec / BC specific rules, US carrier obtaining Canadian operating authority, FAST card for drivers, customs (CBSA), Health Canada hazmat, and how Transport Canada equivalents differ from US FMCSA. Reference USMCA + Transport Canada NSC 14.

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

Use this skill if your operating authority has been revoked and you need to reinstate. Covers application, fees, and timeline.

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

Use this skill when the user asks the difference between a freight broker, freight forwarder, and motor carrier (49 CFR 371 + 373) — required authority for each, bond requirements (BMC-84 broker bond, BMC-85 freight forwarder bond), broker-carrier agreements, factoring + commissions, double brokering, and how to identify each role on a Bill of Lading. Cite 49 CFR 371 + 373.

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

Plan and diagnose FIPA-style ontology-service interactions while keeping declared ontology relations, provider capability, and application authorization separate. NOT for treating an ontology mapping as provider authority or guaranteed interoperability.

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

Designs, reconciles, and reviews an end-to-end Drydock program for safely staging agent runtimes: immutable worktree provenance, disposable VM containment, typed effect brokerage, global body accounting, resurrection, subscription-capacity economics, context compaction, operator control, evidence, and promotion. Use when several Drydock contracts must compose into one architecture, implementation hypertree, diagram set, or release plan. NOT for launching Port Daddy, running an untrusted subject, replacing focused containment/resurrection/capacity audits, or treating a design packet as runtime authority.

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

Design dashboards for migrations and runtimes. Use for authority drift, verifier status, burn-down, runtime health, or pain panels. NOT for vanity analytics, ad hoc charts, or duplicate reporting.

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

Interpret and design bounded FIPA communicative-act exchanges using XC00037H semantics while keeping delivery, authority, and external effects separate. NOT for proving delivery, task authorization, or external effect completion.

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

Apply GPGP/TAEMS coordination as local-scheduler constraints under explicit task, view, commitment, and delivery assumptions. NOT for assuming global task visibility, reliable delivery, or modern execution authority.

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

Design and validate versioned DAGs with typed dependencies, gates, and evidence-bound readiness. NOT for executing a DAG, granting work authority, or treating an unverified gate as cleared.

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

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.

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

Plan or audit the cross-layer Harbor cooperative editor: Loro replicas for humans and agents, governed edit claims, salvage authority, and transport across shared, LAN, and remote harbors. Use when a change spans editor collaboration, identity, recovery, or transport contracts. For a single GPUI pane use gpui-rust-console; for motion use rust-gpui-motion; for a shader use gpui-shaders. NOT for non-collaborative screens, web editors, or generic Rust development.

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

Design AgentSpeak-style BDI plan libraries with explicit event, context, failure, and authority boundaries. NOT for treating BDI plans as safety approval or guaranteed execution.

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