708건 · 관련도순
Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenClaw CI의 대기와 실행 환경 부족 원인을 조사합니다. 측정 결과에 따라 실행기 등록 수, 병렬 실행 수, 테스트 분할과 작업 배치를 조정합니다.
대규모 기능의 설계 제안을 의존 관계와 통과 기준이 있는 작업으로 나눕니다. 여러 에이전트의 조사, 구현, 테스트, 검토부터 통합과 최종 검증까지 정리합니다.
실시간 화면과 데이터 전달의 지연, 데이터 최신성, 처리 대기를 따로 측정합니다. 이벤트 발생부터 화면 표시까지 경로를 개선하고 운영 환경에서 결과를 확인합니다.
Manage ComfyUI image generation from the command line. Validate workflows, which define generation steps, submit them for execution, monitor queued jobs, inspect available models, and download images from completed runs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Move slow Python operations into background jobs so requests can return promptly. Use task queues and workers, the processes that execute queued work, with retry rules, duplicate handling, time limits, and persistent job status.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Size support and operations teams using demand ranges and queueing calculations, which estimate how work waits for service. Assess workload imbalance and service target risks, then build a quarterly hiring plan that accounts for training time and attrition.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use the Archon CLI to launch AI workflows on projects, inspect their results, and approve, reject, cancel, or resume runs. The skill also guides setup, configuration changes, workflow creation, and improvements to workflow prompts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run batch processing, scientific simulations, and machine learning training on Google Kubernetes Engine. Configure parallel jobs, queues that manage resource access, and distributed computation, with guidance on scaling idle capacity down and recovering from interruptions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and manage Volcano jobs and scheduling queues in KubeSphere. Use YAML templates for PyTorch, TensorFlow, MPI, and batch workloads, configure resource requests and execution policies, and investigate jobs that remain pending or fail to create pods.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Advance one development task by managing an existing pull request, fixing a build failure or bug, or implementing a queued idea. Record the work and integrate changes into auto-dev only after automated checks pass.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill for hands-on DOCA Ethernet packet-queue work on a BlueField DPU or ConnectX NIC — bringing up a `doca_eth_rxq` or `doca_eth_txq` on a port / representor / SF, picking among the four `enum doca_eth_rxq_type` values (`_REGULAR` / `_CYCLIC` / `_MANAGED_MEMPOOL` / `_SHARED_MEMPOOL`), sizing burst or scatter-gather length against the `_cap_*` queries, submitting `doca_eth_txq_task_send` / `_lso_send` (carrying packet `doca_buf`s — no `doca_eth_frame` struct exists), or debugging DOCA_ERROR_* from an Ethernet call. `doca_eth_rxq` and `doca_eth_txq` are two Core contexts; one `doca_ctx_start()` does not cover both. Trigger on implicit phrasings: "my RX queue is up but no packets arrive", "send-task returns AGAIN at line rate", "which queue type for fixed-MTU ingress", "device open fails without sudo", or "is L3 checksum offload available here". Refuse and route elsewhere for installing DOCA, flow-rule / steering programming, host↔DPU control messaging, or RDMA data movement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Graphile Worker expert for high-performance PostgreSQL job queues with trigger-based job creation and millisecond job pickup via LISTEN/NOTIFY. Use when "graphile worker, postgres trigger job, listen notify queue, postgraphile worker, database trigger queue, transactional job, graphile-worker, postgresql, triggers, listen-notify, job-queue, postgraphile, high-performance, supabase" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an "enable observability" card asks for queues, or a worker's queue.backlog / consumer lag signals are unbound - which exporter or direct broker data source reads Kafka, RabbitMQ, NATS and Redis queues, the metric names the recipes expect, and the consumer-side metrics the developer adds
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only config drift, and payload-to-side-effect chains. Use when the user asks to trace a queue payload, inspect async job execution, explain worker-only behavior, follow retries or dead-letter handling, or connect an enqueued item to a later file, cache, email, or privilege-bearing side effect. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work with the @upstash/qstash TypeScript/JavaScript SDK, an HTTP-based message queue, task scheduler, and background job system for serverless and edge runtimes (Next.js, Vercel, Cloudflare Workers, Deno, Node.js). Use when publishing messages to HTTP endpoints or URL groups, running background jobs without a long-running worker process, scheduling with cron expressions, delaying messages, building FIFO queues with parallelism and flow control, configuring retries and callbacks, handling a dead letter queue (DLQ), deduplicating messages, fanning out to multiple endpoints, verifying QStash webhook signatures (Next.js App Router, Pages Router, and Edge Runtime), running a local QStash dev server, or migrating regions. Also use when the user asks for a serverless cron job, async task queue, job scheduler, delayed delivery, webhook delivery with retries, or event-driven messaging between services.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Windows アプリ開発 (WinUI 3 / Windows App SDK) のテスト・性能・アクセシビリティ・スレッド。 MSTest, xUnit, NUnit, WinAppDriver, Appium, Playwright, WebView2 テスト, CI, WACK, MSIX サイドローディング, version adaptive。LoggingChannel / ETW, WPT, WPA, プロファイリング, GC, 起動性能, XAML 最適化, ListView/GridView 仮想化。UI Automation, AutomationProperties, automation peers, キーボード操作性, ハイコントラスト, Narrator。DispatcherQueue, DispatcherQueueTimer, WinRT 非同期パターン, async/await, ConfigureAwait, スレッドプール, STA/MTA, デッドロック回避, バックグラウンドタスク。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BullMQ (Node.js ジョブキュー、Redis / PostgreSQL バックエンド対応) リファレンス。 Queue, Worker, Job, FlowProducer, QueueEvents、PostgreSQL backend、 createPostgresBackend, withBackend、レート制限、cron、delayed / repeatable / priority ジョブ、 再試行、デッドレター、フロー、バッチ処理、メトリクス。Python / Elixir / PHP / Rust 対応。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.