「scheduled」の検索結果

Router for the 63 SfSkills `flow` skill packages. Flow Builder: record-triggered, screen, scheduled and orchestration flows, bulkification, fault handling, limits, testing. "My flow" belongs here even when salesforce-apex also names the limit. Nightly scheduling without naming code defaults here; apex takes it when code/class/Apex is named. Flow-vs-Apex choice before anything is built: admin/process-automation-selection. Use when the request mentions Flow, Flow Builder, record-triggered flow, screen flow, scheduled flow, subflow, fault path, flow element, orchestration, Process Builder migration, Workflow Rule migration, flow limit, flow hitting SOQL limit, too many SOQL queries in a flow, flow bulkification, Get Records performance. Finds and opens the exact skill package to read; it does not contain the guidance itself.

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

Check that the scheduled data work behind the reports actually ran and produced something sensible: the daily reshaping scripts, the API pulls, the tables the reports read from. Use each morning before anyone opens a report, when a report looks wrong and nobody knows whether it is the data or the query, after a schema or API change, when a new audience or source is added to the pipeline, or when a scheduled job failed or finished suspiciously fast.

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

Transform Claude Code into a fully autonomous agent system with persistent memory, scheduled operations, computer use, and task queuing. Replaces standalone agent frameworks (Hermes, AutoGPT) by leveraging Claude Code's native crons, dispatch, MCP tools, and memory. Use when the user wants continuous autonomous operation, scheduled tasks, or a self-directing agent loop.

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

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

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

Transition insulin pump to scheduled subcutaneous basal bolus insulin when anticipated hospital length of stay exceeds 1 to 2 days and pump expertise is unavailable. Triggers include: "Patient expected to stay >2 days, should we switch pump to scheduled insulin?

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

Safely integrate with WooCommerce Subscriptions renewal, next-payment scheduling, Action Scheduler events, and retry flow. Shows when to use WC_Subscription::update_dates, update_status, wcs_create_renewal_order, wcs_renewal_order_created, woocommerce_scheduled_subscription_payment, woocommerce_scheduled_subscription_payment_{gateway_id}, woocommerce_subscription_renewal_payment_complete, and payment retry hooks. Use when changing next payment dates, forcing/rescheduling renewals, reacting to failed renewals, building gateway recurring charge logic, or debugging missing/duplicate renewal orders.

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

Curated WooCommerce Subscriptions hook and extension-point map for choosing the right action/filter around WC_Subscription creation, status transitions, date changes, renewal orders, scheduled payments, payment retries, gateway events, switching, gifting, related orders, REST/API responses, and account/admin UI. Use when the user asks for a Woo Subscriptions hook list, "where should I hook", "after renewal", "subscription status changed", or when code contains WC_Subscription, wcs_create_subscription, wcs_create_renewal_order, woocommerce_scheduled_subscription_payment, wcs_renewal_order_created, payment_retry, wcs_get_subscriptions, wcsg_, subscription_switch, _subscription_switch_data, _recipient_user, wcsg_recipient, or subscription switching.

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

Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, scheduled http, message queue serverless.

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

Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).

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

Claude Code (code.claude.com) の拡張機能リファレンス。 Agent Skills (SKILL.md), slash commands, output styles, subagents, agent teams, agent view, workflows, routines, scheduled tasks, hooks (PreToolUse / PostToolUse), plugins, plugin marketplace, MCP 設定 (.mcp.json / claude mcp add), managed MCP, channels (--channels / claude/channel push events, webhook / telegram / discord / imessage), tools-reference, advisor, ultrareview。

Claude Code (code.claude.com) の各サーフェス（Desktop / IDE / Web / モバイル / ターミナル UX）リファレンス。 Desktop app（launch.json, scheduled tasks, WSL, Linux, iOS simulator）、 VS Code / JetBrains / Chrome 拡張連携、claude.ai/code（Web）と mobile アプリ、 interactive mode, fullscreen, voice dictation, accessibility, computer use, artifacts。

Gate scheduled work on Claude usage limits — /mxm-tasks schedule, run-cycle, scheduled task fire time, background batch dispatch. Checks 5-hour and 7-day usage before firing and sleeps until reset when over threshold.

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

Comprehensive persistence tradecraft for authorized red team engagements covering Windows and Linux mechanisms. Windows techniques include registry Run/RunOnce keys, scheduled tasks, WMI event subscriptions, DLL search order hijacking, COM object hijacking, Startup folder drops, service creation, Security Support Provider (SSP) DLL injection, and Active Directory persistence (AdminSDHolder abuse, DCShadow, Golden Ticket, Silver Ticket, Skeleton Key, SID History injection). Linux techniques include cron and at jobs, systemd timers and services, SSH authorized_keys injection, shell profile backdoors (.bashrc/.bash_profile), PAM module backdoors, LD_PRELOAD hijacking, kernel module rootkits, web shells, and Git hook abuse. Provides operator-ready command sequences for SharPersist, Impacket ticketer, schtasks, sc.exe, crontab, and systemctl with OPSEC considerations for each method. Maps to MITRE ATT&CK T1547 (Boot or Logon Autostart), T1053 (Scheduled Task/Job), T1546 (Event Triggered Execution), T1556 (Modi...

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

Laravelの環境設定からコード検査、テスト、依存関係の脆弱性、データベース変更、キューまで順に確認し、マージやデプロイ前の問題を調べるスキル。

• Laravelのプルリクエスト前の確認
• 大きな改修や依存関係更新後の検証
• ステージング・本番へのデプロイ前確認

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

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

公開サイトやAPIから求人・価格・ニュースなどを定期収集する仕組みを作ります。AIによる要約・分類・採点、保存先との連携、利用者の評価を次回に反映する設計も扱います。

• 求人を収集して条件との一致度を採点
• 商品価格を定期的に追跡したいとき
• ニュースを収集して話題別に分類

定期ジョブ、フック、MCPサーバー、外部連携などの設定と稼働状況を証拠付きで棚卸しし、故障や重複、不足を整理して、維持・統合・廃止・修正の優先順位を示すスキル。

• 実際に動いている自動化を確認したいとき
• 故障したジョブや認証切れを探したいとき
• フック・スクリプト・外部連携の重複整理

クラウド上のGPUで機械学習の学習・推論を実行し、モデルをAPIとして公開するスキル。Pythonで実行環境を定義し、並列処理や定期実行も設定できます。

• GPUサーバーを管理せず学習したいとき
• モデルを自動拡張するAPIとして公開
• 大量のデータを並列処理したいとき

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

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

Composite Phase-2 audit worker (ADR-150). Bundles harness oia-manifest + threat-model + mcp-scan into one timestamped audit record stored in the `metaharness-audit` memory namespace. Designed for cron-scheduled drift detection.

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

Create or update a scheduled task that runs automatically. Use when the user says things like "every day", "each morning", "remind me in an hour", "run this at noon", or wants to reschedule an existing task.

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

Review a ChatGPT Space page and its schedules, recommend useful recurring work, and create, update, or remove scheduled automations.

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

Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule.

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

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

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