'routing' 검색 결과

Configuring Salesforce Omni-Channel routing from scratch or updating existing routing: enabling Omni-Channel, creating Service Channels, configuring Routing Configurations (queue-based and skills-based), setting up Presence Statuses and Presence Configurations, assigning skills to Service Resources, and defining Skills-Based Routing Rules. Trigger keywords: Omni-Channel setup, routing configuration, queue-based routing, skills-based routing, presence status, service channel, routing rules. NOT for agent capacity units and channel weighting — use architect/omni-channel-capacity-model. NOT for Apex routing via PendingServiceRouting — use apex/omni-channel-custom-routing.

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

Configuring Salesforce Email-to-Case: Standard vs On-Demand mode selection, routing address setup, email threading via Lightning tokens, auto-response rules, attachment limits, and per-address case field defaults. Trigger keywords: email-to-case, routing address, on-demand email-to-case, email threading, case from email, email agent, routing address setup, Case.settings-meta.xml, EmailToCaseRoutingAddress, emailServicesAddress, isVerified, caseOrigin, enableThreadTokenInBody, useEmailHeadersForThreading, overEmailLimitAction, unauthorizedSenderAction, enableE2CAttachmentAsFile, saveEmailHeaders, newEntityRecordType, casePriority, EmailMessage.EmailRoutingAddressId, auto-response loop. NOT for the wider case layer (queues, escalation rules, case teams, entitlements) - use admin/case-management-setup. NOT for routing case work items to agents after creation - use admin/omni-channel-routing-setup. NOT for the email templates or letterheads themselves - use admin/email-templates-and-alerts.

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

Universeller Skill für LLM-Navigation, Orientierung und Ausfallsicherheit. Stellt aktives Wayfinding, Selbstorientierung und Wiederherstellungsheuristiken bereit, wenn Agenten mit Kontextdrift, fehlschlagenden Werkzeugen, Schleifen oder Sackgassen konfrontiert sind. Enthält die synonymen Strategien survival-routing, dead-reckoning, pathfinder-routing und celestial-routing.

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

Eigenständige Navigations- und Routing-Strategie, die Verzeichnishierarchien nach oben und unten nach Wegweiser-Dokumenten wie CLAUDE.md, AGENTS.md, README.md und RULES.md sowie nach nutzerkonfigurierbaren Stichwörtern durchsucht. Die Konfiguration erfolgt über staircase-config.json oder config.json. Auch als Up-and-Down Routing oder Walking Bass Routing bekannt.

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

Create, list, switch, and delete model routing combinations from the command line. Request suggestions using task descriptions, cost limits, and response time limits, with an option to explain recommendations or activate a suggested setup.

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

• Creating a routing combination with specified models
• Listing routing combinations and switching the active one
• Finding candidates within cost and response time limits

Group AI providers and models behind one model ID in OmniRoute. Choose among 19 routing strategies, define fallback sequences for failures, simulate which provider will be selected, and inspect latency, success rates, and costs.

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

• Call multiple AI models through one model ID
• Configure fallback order for failures
• Simulate routing decisions before making API calls

Assign unowned leads and opportunities using company routing rules and existing account relationships. Prepare a recommendation with its reasoning, draft handoff notes, and apply ownership changes after a person accepts or overrides each recommendation.

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

• Assigning newly received leads to sales representatives
• Reviewing a queue of unassigned opportunities
• Preparing handoff notes with assignment reasons

TanStack Router best practices for type-safe routing, file-based routing, data loading, search params, and navigation in React. Use when building React SPAs with complex routing, implementing type-safe search params, setting up route loaders, integrating with TanStack Query, or configuring code splitting and preloading.

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

Inbound email processing in Salesforce via Email Services + the `Messaging.InboundEmailHandler` Apex interface. Covers EmailService configuration (running user, accept-from address, attachment handling, error / failure routing), the EmailServicesAddress per-routing-address pattern, the handler's `Messaging.InboundEmail` payload (text body, HTML body, headers, attachments, in-reply-to threading), and the canonical Email-to-Case alternative for case creation. NOT for outbound email (use admin/email-templates-and-alerts), NOT for Email-to-Case flow customization itself (use admin/email-to-case-configuration). Trigger keywords: EmailServicesFunction, EmailServicesAddress, runAsUser, localPart, EmailDomainName, attachmentOption, overLimitAction, errorRoutingAddress, routing address, inbound email limit.

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

Domain-aware complexity routing. Scans task description for domain keywords, matches against domain-complexity.csv, returns complexity level, workflow intensity, and execution tier. Extends Phase 0 orchestration.

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

Erstellt und verwendet einen anbieterneutralen semantischen Routing-Graphen aus Personas, koordinierenden Rollen, Experten und aktiven Skill-Endpunkten. Verwenden, wenn ein LLM eine Anfrage von einer Leitrolle über einen Experten zu einem Skill routen, aus einem vorhandenen Agentensystem einen portablen Persona-Router extrahieren, eine semantische Domänenkarte mit einer lexikalischen Skill-Registry kombinieren oder fehlende Verbindungen zwischen Rolle und Skill sichtbar machen soll, statt still auf einen Ersatz zurückzufallen. Auslöser sind unter anderem semantisches Persona-Routing, Persona-Umbrella, Rollen-Router, Boss-Agent-Experten-Skill-Routing, Agentenrollen-Export oder die Wiederverwendung von Personas über mehrere LLM-Anbieter hinweg.

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

Choose an agent and model tier using the task description and learned patterns. The skill can explain its recommendation, use compiler-based edits for supported simple changes, and record task outcomes to inform future routing decisions.

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

• Choose an agent and model before starting a task
• Review the reasoning behind a routing recommendation
• Apply supported code changes through the TypeScript compiler

Investigate web applications in a CTF sandbox by tracing real browser requests, stored state, API calls, and background jobs. Compare successful and failing flows to explain authentication, routing, and differences between interface and server behavior.

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

• Trace authentication and session flows
• Compare browser state with server behavior
• Follow uploads and background jobs

Trace how requests travel through a CTF sandbox, from hostnames and proxy rules to containers and processes. Compare headers and live traffic to identify which service handles a request and what changes its destination.

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

• Identify which container handles a request
• Check how Host and forwarded headers affect routing
• Trace path rewrites and WebSocket routing

Build and train Mixture of Experts models, which activate selected specialist networks for each input. Use DeepSpeed or HuggingFace workflows to configure routing, balance workloads, distribute experts across GPUs, and optimize inference.

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

• Designing MoE models for a limited compute budget
• Implementing Mixtral-style expert routing
• Adjusting expert workloads and training stability

Reduce the size of AGENTS.md or RESOLVER.md by grouping skills into functional areas. Each area keeps a list of its sub-skills, helping the agent find the appropriate skill through a two-level routing structure.

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

• Shortening a large AGENTS.md
• Grouping skill routes by functional area
• Checking routing accuracy after compression

Configure Google Cloud logs across multiple projects, either by storing them centrally or querying them together where they already reside. The skill guides routing, access permissions, and log views, and helps diagnose missing logs and permission failures.

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

• Collect logs from multiple projects in one central bucket
• Query distributed logs without copying their data
• Set log access boundaries by project or log type

Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only. Use when the user is building or solving routing in Python.

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

Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only. Use when the user is building or solving routing in Python.

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

Expert guide for intelligent model cascading and routing — complexity-scored task routing from Flash/Haiku to Sonnet/Opus/Astra, dynamic escalation with quality gates, 40-60% token cost reduction while maintaining output quality / Panduan ahli untuk kaskade dan routing model cerdas — routing tugas berbasis skor kompleksitas dari Flash/Haiku ke Sonnet/Opus/Astra, eskalasi dinamis dengan gerbang kualitas, pengurangan biaya token 40-60% dengan kualitas output terjaga.

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

Use this skill when configuring or troubleshooting Lead or Case assignment rules in Salesforce: creating rule entries, setting filter criteria, assigning records to users or queues, understanding when rules run, and implementing round-robin patterns with Apex. Trigger keywords: lead assignment, case assignment, assignment rule, queue assignment, auto-assign. NOT for creating the queue or public group a rule routes into — use admin/queues-and-public-groups. NOT for Omni-Channel or skills-based routing — use admin/omni-channel-routing-setup. NOT for approval routing — use admin/approval-processes.

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

Cloudflare Email Service（Email Sending + Email Routing）でトランザクションメールの送受信を実装するスキル。Workers bindingまたはREST APIによるメール送信、Email Routing、Agents SDKのemail handler、Workers・Node.js・Python・Go等への組み込みで使う。到達性、SPF/DKIM/DMARC、wrangler email設定、MCP email tools、coding agentからのメール送信も対象。「Workerにメール機能を追加」のような依頼でも、重要な設定要件があるため必ず使用する。

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

Implements type-safe Flutter routing using AutoRoute v11 with code generation and @RoutePage annotations. Activates when setting up AutoRoute navigation, configuring AutoRouterConfig or RootStackRouter, generating route files with build_runner, using @RoutePage, @PathParam, or @QueryParam annotations, implementing AutoTabsRouter for bottom navigation tabs, adding navigation guards with AutoRouteGuard, setting up nested or child routes, handling type-safe route parameters, or migrating from string-based Navigator routing to compile-time-verified routes. Ideal for large apps requiring refactoring confidence and zero string-based routing errors.

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

Create HTML slides about choosing and connecting AI models in OpenDesign using your own API key. Use a terminal-style template to explain costs, quality, and model routing decisions, with speaker notes and presentation controls.

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

• Explaining model choices to engineers and IT teams
• Comparing model costs, quality, and routing decisions in slides
• Preparing a terminal-style presentation with speaker notes