'queues' 검색 결과

Build Python applications that keep other tasks moving while waiting for network, file, or database operations. The skill guides asyncio patterns, task cancellation, timeouts, workload limits, and testing for asynchronous APIs, scrapers, and background processing.

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

• Building asynchronous web APIs
• Sending concurrent requests in web scrapers
• Designing background tasks and queues

Coordinates specialist agents in Claude Code to work from product requirements through design, implementation, testing, deployment, and operations. Includes task queues, saved progress, parallel reviews, and recovery workflows for managing extended development work.

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

• Turning product requirements into development tasks
• Coordinating implementation, testing, and reviews
• Resuming extended work from saved progress

Prepare overdue invoice reminders using accounting records and recent payment data. Adjust each message to the customer's payment history, flag possible payments for checking, and send through PayPal or queue email drafts after approval.

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

• Checking which customers have overdue invoices
• Adjusting reminders to each customer's payment history
• Checking for recent payments before sending reminders

Draft prospect emails and follow-up sequences using the sender’s established writing style and specific facts about each recipient. Present messages for approval, prepare approved sends when connected, and record contact history in HubSpot or a file.

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

• Draft a cold email in the sender’s own style
• Prepare outreach to a referred prospect
• Write follow-ups after a customer meeting

Analyze business workflows to find delays, repeated work, unnecessary steps, and opportunities for automation. Get a before-and-after process comparison, specific recommendations, estimated effects, and an implementation plan based on how the work currently happens.

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

• Investigating delays caused by approval queues
• Simplifying workflows with too many steps
• Reducing repeated work and handoff problems

Prepare legal work briefings from connected email, calendars, documents, and contracts. Choose a daily overview, an internal topic review, or an incident summary, with urgent items, relevant background, information gaps, and suggested next steps.

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

• Review urgent legal work and upcoming deadlines each morning
• Summarize internal records on a specific legal topic
• Gather initial context for a data breach or dispute

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.

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

• Estimate staffing for support and operations queues
• Check workload imbalance and service target risks
• Build quarterly hiring plans with ramp 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.

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

• Running an AI workflow to address an issue
• Asking Archon to review a pull request
• Inspecting, approving, or resuming a run

Manages security incident cases in Google SecOps, from reviewing queues and related alerts to updating priorities, assignments, and investigation notes. It supports closing cases with documented causes, with available actions depending on the connected MCP tools.

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

• Reviewing open cases with high priority
• Inspecting related alerts and affected entities
• Recording findings and updating case assignments

Design iii backends by combining functions, queues, and shared state. Choose patterns for workflows with retries, live updates, cooperating AI agents, and event-driven processing, with examples showing how the pieces connect.

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

• Designing order workflows with retries and step tracking
• Updating screens or caches when stored data changes
• Passing tasks between specialized AI agents

Automate tmux, a tool for managing multiple terminal workspaces, to inspect output, send commands, monitor stalled tasks, and record logs. Coordinate multiple AI terminals with task queues, file locks, status tracking, and handoff reports.

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

• Inspect output and errors across multiple AI terminals
• Resume tasks waiting for confirmation
• Coordinate tasks and file locks across AI workers

Build Laravel applications with authenticated APIs, interactive interfaces, and background jobs. The skill guides database relationships, query optimization, and feature tests, using tools such as Sanctum for authentication and Livewire for interfaces.

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

• Build an authenticated Laravel API
• Optimize database queries and relationships
• Set up background jobs with Horizon

Classify agent work as ready to continue, needing human judgment, or intentionally paused. Structure decision requests with evidence, a recommended choice, and clear outcomes, then connect the recorded decision to the next responsible agent.

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

• Deciding whether agent work needs human review
• Preparing decision requests with evidence and recommended choices
• Designing a dashboard for pending human decisions

Execute an existing Ouroboros Seed, a specification containing a goal and acceptance criteria, as a background job. The workflow checks each criterion, normally queues formal evaluation, and follows a bounded improvement loop if evaluation rejects the result.

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

• Executing an existing Seed specification
• Checking whether each acceptance criterion is met
• Following execution, evaluation, and improvement results

Find the relevant architectural guidance for API design, security, cloud infrastructure, message queues, and caching. This skill acts as an index to specialized references and lists principles for structuring software, distributed systems, and access controls.

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

• Finding guidance for API design
• Reviewing security architecture topics
• Exploring containers, K8s, and Serverless

Add OpenTelemetry tracing to frontend and backend flows. Connect execution records across services and background jobs, record phase durations and entity IDs, and mark failures so developers can investigate slow or broken operations.

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

• Tracing a user action across multiple services
• Investigating slow queues and background jobs
• Connecting missing or disconnected traces

Administers Observal users, settings, diagnostics, review queues, security events, audit logs, SAML, SCIM, the local Observal server, its upgrades and rollback, and its own PostgreSQL and ClickHouse schema migrations. Use when the user needs privileged governance, submission decisions, identity configuration, security investigation, or Observal server operations. Not for querying a database or any work outside Observal administration.

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

Read 微信公众号 articles from mp.weixin.qq.com links using available web or browser tools. Report verification walls honestly; reading alone does not modify notes or queues.

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

Process-based discrete-event simulation framework in Python. Use this skill when building simulations of systems with processes, queues, resources, and time-based events such as manufacturing systems, service operations, network traffic, logistics, or any system where entities interact with shared resources over time.

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

Operate the DOCA UROM Service container on BlueField Arm for remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using `doca-urom`: pull the NGC image, choose the UCX component, size queues, configure Comch pairing, and align host and service versions. SECURITY: the service has no standalone access control; Comch pairing and RDMA permissions are the boundary. Pair only intended hosts, expose least-privilege memory regions, and verify both views before start. Trigger for slow UCX collectives, unexpected NOT_PERMITTED, or missing completions. Do not use for host application code, MPI/UCX integration design, or DOCA install.

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

DOCA Rivermax (doca_rmax) receive streams for timing-precise media over IP (SMPTE ST 2110 video / audio, market data, scientific feeds) on a BlueField DPU or ConnectX host, once the Rivermax SDK and its license are installed; getting the SDK or license is doca-setup / doca-public-knowledge-map territory. Trigger on "ST 2110 receive isn't getting frames", "sub-microsecond jitter on my media receiver", "NOT_SUPPORTED from doca_rmax_init", "no recv events after stream start", or "license check failing on a media receiver", even without naming Rivermax. Covers doca_rmax_in_stream sessions, the SDK + license precondition check, doca_rmax_get_*_supported capability queries, pairing with doca-eth queues and doca-flow steering, and DOCA_ERROR_* from Rivermax calls. Refuse and route elsewhere for programming the underlying queue (doca-eth), steering rules (doca-flow), PTP / clock sync (doca-firefly), or best-effort packet I/O.

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

Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LD_LIBRARY_PATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA install from a host that doesn't have one yet via the NGC DOCA container Stage-1 fallback. Trigger even when the user does not explicitly mention "DOCA setup" — typical implicit phrasings include "just got a BlueField, what now", "code is built, how to run it", "pkg-config can't find doca-flow", "no free 2048 kB hugepages", "representor X not found", "on a Mac and want to learn DOCA". Refuse and route elsewhere for library API specifics (Flow pipes, RDMA queues), the modify-a-sample first-app workflow or DOCA_ERROR_* program-side debugging, and "where is X documented" knowledge-map questions — those belong to other skills.

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

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.

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

Use this skill for hands-on DOCA GPI programming — wiring a GPU-Packet-Initiator context so a CUDA kernel drives RDMA queues directly from GPU memory without host CPU mediation. Covers picking GPI vs doca-gpunetio, the doca_gpi / domain / channel object model, the GPU-side handle handoff (doca_gpu_gpi_channel*), attaching GPU memory to a GPI domain, the domain and channel attribute objects, and debugging DOCA_ERROR_* from doca_gpi_* calls. Trigger even when the user does not explicitly mention "DOCA GPI" — implicit phrasings include "my CUDA kernel needs to post RDMA directly from GPU memory", "DOCA_ERROR_* from doca_gpi_gpu_channel_get", "how do I hand a GPU handle to my CUDA kernel", "how many channels can a GPI domain hold", or "GPU kernel driving RDMA without the host CPU on the path". Refuse and route elsewhere for the doca-gpunetio Send/Receive surface, the doca-rdma queue lifecycle, DPA-side initiation (doca-rdmi), or the CUDA programming model — those belong to other skills.

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