「delivery」の検索結果

Redisを使ったキャッシュ、アクセス回数制限、複数処理の同時実行制御、メッセージ配信を設計し、キーの有効期限や接続管理も見直すスキル。

• APIにキャッシュを追加したいとき
• 利用者別にアクセス回数を制限
• ワーカーのジョブ同時実行を防止

工場の設備・人員・材料・納期を踏まえて生産順序を組み、段取り替えや工程間の負荷を調整し、設備故障や材料不足時の計画見直しを支援するスキル。

• 限られた設備での生産順序の検討
• 設備故障後に計画を組み直したいとき
• ロット量と段取り替え費用の比較

配送の遅延・破損・紛失・数量不足に対し、証拠収集から補償請求、運送会社との交渉までを整理し、損失額や顧客への影響に応じた対応判断を支えるスキル。

• 配送の遅延や紛失に対応したいとき
• 貨物破損の補償請求を準備したいとき
• 運送会社の料金や責任を争うとき

Claude Codeの終了時に学習記録の更新日時やディスク空き容量を確認し、条件に応じて完了を止めるスキル。会話中の手順省略を示す表現にも警告します。

• 複雑な編集後に学習記録を確認したいとき
• 空き容量不足で完了を止めたいとき
• 確認省略を示す表現の検出

顧客や取引先が参加するチャットで、エージェントの応答条件と送信内容を定めるスキル。呼びかけへの応答、内部情報の保護、承認用の下書きへの切り分けを扱います。

• 顧客グループでの応答ルール設定
• 取引先への返信から内部情報を守りたいとき
• 価格や契約の回答を承認用下書きに分ける

Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection. Use for new integration research and delivery; not for ad hoc connector coding that bypasses the playbooks.

日本語の概要は準備中です。原文の説明を表示しています。

For consulting delivery work: turn diagnosis, frameworks, and project work into a client-adoptable action plan. Built around the core query "consulting-final-deck", with engagement manager judgment, buyer-ready proof, and this outcome: accept the recommendation and commit owners to the roadmap.

日本語の概要は準備中です。原文の説明を表示しています。

Register, list, test, and remove webhook endpoints. Configure event subscriptions (request.completed, request.failed, quota.exceeded, etc.) and manage delivery retries.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing the image pipeline, static assets in `public/`, CMS-managed media, or image CDN transforms. Separate file-size problems from dimension mismatches so you can tell whether the issue is compression, format choice, or responsive delivery.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing slow page loads, heavy assets, or rendering delays related to Use a content delivery network. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

日本語の概要は準備中です。原文の説明を表示しています。

Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the smallest atomic, independently-mergeable PRs and builds the independent ones concurrently via one worktree per PR driven by parallel subagents or a team. Unbounded loop: any failing gate sends you back to fix-and-re-QA inside that PR's worktree. Use whenever implementation work needs to land as a PR. Triggers: 'create a PR', 'implement and PR', 'work on this and make a PR', 'implement issue', 'land this as a PR', 'split into atomic PRs', 'parallel PRs', 'work-with-pr', 'PR workflow', 'implement end to end', even when user just says 'implement X' if the context implies PR delivery.

日本語の概要は準備中です。原文の説明を表示しています。

QA the omo Senpi adapter (packages/omo-senpi, packages/senpi-task) against the REAL senpi binary in strict isolation, and write every artifact to the one canonical evidence path .omo/evidence/omo-senpi-adapter/<slug>/. The live drivers under packages/omo-senpi/scripts/qa/ create their own isolated SENPI_CODING_AGENT_DIR and ignore the caller's, so the real ~/.senpi/agent is never written. Ships scripts/resolve-evidence-dir.mjs, which is the ONLY sanctioned way to pick an evidence directory: it rejects traversal, separators, absolute paths, and stray roots such as local-ignore/qa-evidence. Use whenever someone changes anything under packages/omo-senpi or packages/senpi-task, or wants to QA, smoke-test, verify, or debug the Senpi adapter, the task/team engine, the DAG, task RPC, or skill delivery. Triggers: senpi qa, qa senpi, senpi-qa, test senpi adapter, verify senpi task, senpi task e2e, senpi team e2e, task dag qa, live senpi driver, senpi evidence path.

日本語の概要は準備中です。原文の説明を表示しています。

Build, revise, or manipulate a fixed-layout PDF (report, guide, one-pager, printable document). Use whenever a build task's artifact kind is pdf, a document build's output format is pdf, or the task reads, merges, splits, crops, or fills an existing PDF, including fillable AcroForms. Covers authoring the print-CSS HTML source, rendering, the geometry and validation gates, existing-PDF manipulation and form filling, and delivery under workspace/your_files.

日本語の概要は準備中です。原文の説明を表示しています。

Use only when all three gates already hold. (1) This same user turn explicitly says to start, implement, build, scaffold, or go ahead with a new project now; prior answers, planning, decisions, and reminders never authorize. (2) No named path or confirmed suitable here/current-folder target resolves placement. (3) Inspection is forbidden, or permitted top-level inspection has already proved the current root home-like, general-purpose, or falsely empty. Do not load this skill merely to check eligibility. Exclude existing work, bug fixes, component edits, server or verification work, and standalone, paste-ready, single-file, or snippet delivery.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare restaurant food orders for delivery or pickup; use for cart, checkout and tracking. Placing the order requires authorization.

日本語の概要は準備中です。原文の説明を表示しています。

Read or triage email, clean up an inbox, draft or send messages, and check delivery. Use for the user's connected mailbox or your own email, including questions about its availability; choose the correct sender and follow the confirmation policy.

日本語の概要は準備中です。原文の説明を表示しています。

Complete automated literature discovery pipeline: multi-source search → six-dimension scoring → fine reading → formatted delivery → archival. Combines a configurable engine with daily cron-driven application layer. Works with Feishu, Telegram, or any messaging platform.

日本語の概要は準備中です。原文の説明を表示しています。

Improve factual reliability while creating or reviewing a course or supplied content. Use when the user asks to fact-check, verify accuracy, reduce hallucinations, make a reliable course, or mentions 事实性错误、知识性错误、专业知识准确性、可靠性. During creation, checks the completed pages before delivery; on existing content, returns a short evidence-backed report and lets the user choose what to fix. Not for grammar, style, or layout. Combine with deep-research when current evidence is the course's main subject.

日本語の概要は準備中です。原文の説明を表示しています。

Chinese K-12 core-literacy course design for a single OpenMAIC classroom. Use when a teacher asks for 中小学课程、核心素养、素养导向、2022 课标、真实情境、任务群、表现性评价, or wants a grade-and-subject lesson designed around authentic tasks rather than content delivery. Covers Chinese, mathematics, languages, science, humanities, technology, arts, PE and labor education across primary, junior-high and senior-high stages.

日本語の概要は準備中です。原文の説明を表示しています。

Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Enforce output quality, evidence verification, and quality gates across security audits. Use this skill when you perform SAST, SCA, threat modeling, or security code reviews. Use this skill to verify code locations and taint traces for all findings. Use this skill to prevent the suppression of valid security findings. Use this skill to evaluate reports against quality thresholds (score ≥ 8/10) before delivery.

日本語の概要は準備中です。原文の説明を表示しています。

The yard's skill map — which skill owns which job, in delivery-loop order. Use when something needs doing but not which of the shipped skills owns it; the map routes, it never executes.

日本語の概要は準備中です。原文の説明を表示しています。