'delivery' 검색 결과

Prepare a local browser app or standalone browser file for handoff. Verify its start behavior where supported, then provide exact commands and a reachable URL, or the artifact path, with an honest account of what was checked.

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

• Hand off a local browser app with verified start instructions
• Deliver a single-file app with a basic startup check
• Share a playable browser game with clear access instructions

Coordinate project delivery by routing requests to eight specialist skills or running a verified delivery workflow. Use live Jira data for progress analysis and completion forecasts, with recorded evidence and checks before tasks are closed.

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

• Analyze sprint progress and forecast completion ranges
• Produce project health reports from live Jira data
• Route Jira permission and configuration reviews

Implement SMS notifications, verification code delivery, and bulk messaging in Java with Azure Communication Services. Covers authentication, asynchronous sending, per-recipient results, error handling, and delivery reports received through Azure Event Grid.

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

• Sending verification codes by SMS
• Adding order notifications and alerts
• Sending the same message to multiple recipients

Review engineering delivery plans, hiring proposals, and team changes through six operational questions. Assess delivery metrics, recruitment stages, management structure, and production practices, then produce a verdict and three concrete actions to address the findings.

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

• Reviewing quarterly delivery commitments
• Checking an engineering hiring plan
• Assessing a proposed team reorganization

[omh] Bot replies via Discord, Slack, or Telegram: normalize Discord, Slack, Telegram, and other gateway sessions into origin, thread, delivery, silent, attachment, and status-update policy. Use when the user says: gateway-intent-card, gateway intent, discord thread, slack thread, telegram delivery, discord delivery policy, slack delivery policy, telegram delivery policy.

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

DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He

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

Configuring or troubleshooting the Nonprofit Success Pack Program Management Module (PMM) - program delivery, cohort setup, service scheduling, service delivery recording, and attendance tracking for beneficiaries. Trigger keywords: program management module, PMM, Program__c, ProgramEngagement__c, ServiceDelivery__c, cohort setup, bulk service delivery, service schedule, service participant. NOT for designing which outcomes and indicators to measure - use admin/program-outcome-tracking-design. NOT for NPSP donor, household and giving-rollup data - use data/nonprofit-data-architecture.

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

Register and manage webhook endpoints, which receive event notifications from OmniRoute. Choose events such as completed requests or exceeded quotas, test delivery, inspect delivery history, and manage retries when notifications need another attempt.

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

• Set up notifications for completed or failed requests
• Configure quota exceeded notifications
• Validate and test notification destinations

Prepare restaurant orders for delivery or pickup by comparing options, building a cart, and checking the full cost and timing. Account for dietary requirements, obtain authorization to order, and confirm acceptance and available tracking details.

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

• Order a usual meal for delivery to a hotel
• Arrange a team lunch with separate dietary needs
• Compare delivery and pickup within a budget

Turn a Zoom integration idea into a practical implementation plan. Identify the required products and APIs, authentication and access permissions, delivery phases, and risks, then define a small first deliverable to test the proposed architecture.

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

• Turning a Zoom integration idea into a build plan
• Clarifying authentication and access permissions
• Planning delivery from prototype to launch

Build automated emails for account registration, invoices, and notifications, from reusable templates to delivery service integration. Includes local previews, multilingual content, dark mode styling, and checks for delivery issues and tracking.

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

• Add registration and password reset emails
• Migrate to another email delivery provider
• Add multilingual content and dark mode

Assess startup engineering operations across delivery, hiring, team structure, and production practices. Use delivery metrics, hiring conversion rates, and staffing data to identify bottlenecks, estimate candidate needs, and plan management roles and operational improvements.

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

• Find where development work waits before release
• Estimate candidate volume needed for hiring goals
• Review team structure and manager hiring needs

Set up and troubleshoot the WizTelemetry Notification extension for KubeSphere. Configure delivery channels such as email and Slack, route alerts by labels, silence notifications for scheduled periods, and search notification history to investigate delivery problems.

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

• Configuring email or Slack alert delivery
• Routing alerts by severity or namespace
• Silencing notifications during maintenance

Guides agents through sending human decision requests and updates using registered recipients. It covers concise briefs, delivery checks, duplicate prevention, and linking replies to the correct work so that delivery receipts are kept distinct from human decisions.

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

• Sending a decision request with clear options
• Reporting an outcome that needs no action
• Investigating a failed or uncertain delivery

Operates Amazon Kinesis Data Streams (KDS). Covers streaming tables and Amazon S3 delivery - serverless, fully managed delivery from a KDS stream to Apache Iceberg tables on S3 Tables or to general-purpose S3 buckets. Includes channel setup, IAM, schemas, output key templates, CloudWatch metrics and alarms, DLQ handling, quotas, and troubleshooting. For all other KDS topics and questions, search AWS documentation and blogs instead. Triggers: Kinesis Data Streams, KDS, streaming tables, stream to S3, stream to Iceberg, stream to S3 Tables, KDS delivery, KDS channel, CreateChannel, data channel, data freshness, dead-letter queue, KDS lakehouse, serverless Kinesis delivery, Firehose alternative for KDS, zero-ops Kinesis to S3. DO NOT USE for Kinesis Data Firehose, Kinesis Video Streams, or Managed Service for Apache Flink — use dedicated skills or search documentation instead.

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

Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines.

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

Provider-independent media quality control and delivery direction for generated images, video, audio, ads, product content, social clips, broadcast and streaming assets, localization packages, and mixed-source edits. Use when an agent must define final export specs, inspect technical and perceptual quality, check captions/audio/color/accessibility/provenance/rights, create delivery sheets, version filenames, checksums, manifests, package deliverables, set acceptance or rejection criteria, and perform final delivery QA before handoff to a platform, broadcaster, streamer, client, or ad trafficker.

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

Analyze flow metrics to identify delivery bottlenecks and improve throughput. Use when the user says "flow metrics", "why is delivery slow", "cycle time analysis", "WIP analysis", "throughput review", "what's our lead time", "DORA metrics", "where is work getting stuck", "Kanban metrics", or wants to diagnose delivery performance using data - even if they don't explicitly say "flow metrics review". Based on "Making Work Visible" by Dominica DeGrandis (WIP limits, flow blockers, time thieves) and "Accelerate" by Forsgren, Humble & Kim (DORA metrics, delivery performance indicators).

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

Extract proof-of-delivery number, recipient, delivery time, items, exceptions, and signature status from delivery receipts.

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

OpenClaw의 QA Lab에서 Telegram 초안과 최종 메시지의 도착 순서를 검증합니다. QA Channel과 실제 Telegram 플러그인으로 같은 시나리오를 실행합니다.

• Telegram 초안과 최종 메시지 전달 확인
• QA Channel에서 전달 흐름 검증
• 실제 Telegram 플러그인으로 검증

SocialClaw로 여러 소셜 플랫폼의 게시물을 예약·발행하고 전달 상태를 확인합니다. 이미지 등 자료 업로드와 여러 플랫폼에 걸친 캠페인 게시 일정 검증도 지원합니다.

• 여러 플랫폼의 캠페인 게시물을 예약합니다
• 게시물에 쓸 이미지 등을 업로드합니다
• 발행 전에 게시 일정을 검증합니다

고객이나 거래처에 보낼 답장 초안을 사람의 승인과 연결하고 승인된 본문, 수신 대상, 전송 결과를 기록합니다. 오래된 승인 사용과 중복 전송을 방지하도록 설계합니다.

• 고객 답장에 사람의 승인 적용
• 승인된 본문과 전송 결과 기록
• 수정 전 승인으로 전송되는 상황 방지

Mailtrap으로 가입 확인과 비밀번호 재설정 메일을 구현합니다. 개발용 테스트와 실제 발송 환경을 분리하고 인증, 도메인 확인, 발송 실패 처리도 다룹니다.

• 가입 확인 메일 추가
• 비밀번호 재설정 메일 구현
• 실제 발송 없이 메일 테스트

Paperclip에서 할당받은 AgentMail 수신함으로 작업에 연결된 메일을 확인하고, 새 메일 전송과 답장, 전송 결과 확인까지 수행합니다.

• 담당 작업에 연결된 메일을 확인합니다
• 할당된 수신함에서 새 메일을 보냅니다
• 대화의 특정 메시지에 답장합니다