「scheduled」の検索結果

Registry of reusable agent sessions and slot allocation: claim a free scheduled-task slot instead of creating a new session, set its prompt and fire time, and release it when done. Use when you need to spawn or reuse a visible background session.

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

⭐ ПРАВИЛО (anton 23.09 голосом): «подними сессию/декомпозируй» адресовано ТЕБЕ = поднимай У СЕБЯ, своими средствами (Cursor → Task-tool/background agents, Codex → свои сессии, Claude → планировщик); нести задачу в другую LLM = ересь. Мост spawn_queue → Claude-планировщик — ТОЛЬКО когда нужна именно видимая scheduled-задача приложения. Триггеры: «подними сессии», «декомпозируй на сессии», lift-spawn.

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

Cut background heat and noise on this machine: audit scheduled tasks by runs per hour, autostart entries, GPU holders, power plan and top CPU, then propose disable or stretch candidates, decide line by line with the operator and apply only approved lines. Triggers: /deflate, fan is loud, laptop runs hot, what can I turn off, machine slow from background load.

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

Pull fresh follow-up call notes from a dedicated Telegram group into the CRM layer of a vault. Incremental and idempotent by message id, safe to re-run, and the manual counterpart of the weekly scheduled job. Triggers: "/faaa-sync", "pull the follow-up notes".

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

Restructure an always-loaded rules file such as CLAUDE.md or MEMORY.md: build a top block of key rules plus numbered categories, move rule bodies verbatim with a script that proves zero byte loss, fold heavy mechanics into trigger-plus-pointer form, then guards, a canary window and fleet rollout. For scheduled maintenance, not ad-hoc trimming. Triggers: "/canon-revision", "revise the canon".

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

Read the system-architect map: a deterministic catalog of everything the setup is made of (vault, import scripts, scheduled tasks, MCP servers, SQLite databases, hooks, skills, dashboards), what is healthy and what fell off. Consult it before changing shared infrastructure and re-scan after. Triggers: "/arch", "/arch broken", "/arch scan", "what broke in the system".

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

WooCommerce Memberships access, restriction, drip-content, product-grant, and member-discount playbook. Use when code checks whether a user can view/purchase content or products, changes scheduled access dates, customizes protected/public content, maps parent or variation products that grant membership access, applies member prices, reads original prices around discounts, or contains wc_memberships_user_can, wc_memberships_access_from_time, wc_memberships_user_has_member_discount, wc_memberships_get_member_product_discount, wc_memberships_get_discounted_price, or member discount badge hooks.

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

Design and review Action Scheduler jobs in WordPress plugins using Action Scheduler 3.9.x public APIs - async, single, recurring, and cron-expression actions; action_scheduler_init load timing; hook/args/group naming; unique and priority parameters; idempotent callbacks; chunked workloads; activation/deactivation cleanup; WooCommerce-bundled or standalone dependency usage; admin and WP-CLI debugging; queue runner limits; and safe operational troubleshooting. Use when a plugin schedules background jobs with as_enqueue_async_action, as_schedule_single_action, as_schedule_recurring_action, as_schedule_cron_action, as_get_scheduled_actions, or integrates with WooCommerce background queues.

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

Daily wisdom review applying Charlie Munger's mental models to your work and thinking. Use when asked to review decisions, analyze thinking patterns, detect biases, apply mental models, do a "Munger review", or run the Munger Observer. Triggers on scheduled daily reviews or manual requests like "run munger observer", "review my thinking", "check for blind spots", or "apply mental models".

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

Use when the user asks to "watch my list health over time", "flag decaying / unengaged subscribers on a schedule", "why is my open rate drifting down / bounces creeping up", or "build me a re-permission and prune worklist"; runs the scheduled SEND list-decay + suppression-drift watch — an engagement-recency cohort read (30/90/180/365-day), hard-bounce and spam-complaint trend vs benchmark, suppression-list growth/leakage check, and a segmented re-permission / sunset / prune worklist tied to SEND S (list hygiene) and E (engagement-decay) sub-items. Not for the one-time pre-send authentication pre-flight — use deliverability-qa; not for the consent/suppression record itself — use consent-registry; not for computing the EQS or enforcing vetoes — use email-quality-auditor. 邮件列表健康度监控/退订漂移/沉睡用户清理

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

Use when the user asks to "build our social crisis protocol", "mentions are exploding — what do we do first", or "when do we pause the posting queue"; produces a 1-5 severity ladder with tunable Estimated trigger thresholds (mention-velocity multiples vs the 7-day listening baseline, sentiment flip, journalist/regulator contact, employee-conduct class), the first-mechanical-action rule — pause ALL scheduled posts AND paid amplification, with dated state markers dropped to the channels proposal protocol and reconciled post-incident — a pre-approved holding-statement library with committed update cadences, when-NOT-to-post rules, a spokesperson/approval matrix, and a post-crisis retro template; re-runs the social-quality-auditor pre-publish gate before un-pausing the queue. Not for email deliverability incidents (blocklist, spam-rate spikes) — use deliverability-qa; inside a launch window launch-day-conductor owns incident handling. 社媒危机预案/暂停队列/声明库/发言人矩阵

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

Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.

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

Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Report-only: findings are produced in the session or as a draft; no scheduled action is taken.

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

Classify incoming issues into the live GitHub label queue, reproduce where cheap, and write an auditable QUEUE.md snapshot. Use when triaging a backlog, running the scheduled triage routine, or deciding what the factory should pick up next.

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

Scheduled health sweep that closes the factory loop - reads CI failures, recent commits, dependency and security advisories, and live queue labels, then files issues and writes an immutable run record. Use for the nightly or weekly monitor routine.

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

Classify GitHub issues into the factory's live label queue and write an auditable snapshot. Use for backlog triage or a scheduled triage run.

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

Generate and send a daily briefing to your owner covering today's meetings, urgent emails, open tasks, and anything that needs attention. Use when: it's the start of the owner's day, when asked for a summary, or on a scheduled cron job.

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

Use when working with Convex — convex backend platform management covering project inventory, table schemas, function deployments, scheduled job status, index configuration, environment variable auditing, and usage metrics. Use for comprehensive Convex project health and resource optimization.

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

Use when working with Cachet — cachet open-source status page management, component tracking, incident reporting, and metric visualization. Covers component group management, incident lifecycle, scheduled maintenance, metric points, and subscriber management. Use when managing self-hosted status pages, creating incidents, tracking component health, or reviewing uptime metrics in Cachet.

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

Use when working with Calendly — calendly scheduling platform management covering event types, scheduled events, invitees, users, and booking analytics. Use when monitoring booking rates, analyzing event type performance, reviewing upcoming schedules, managing Calendly users and teams, or troubleshooting scheduling workflows.

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

Use when working with Atlassian Statuspage — atlassian Statuspage management, component monitoring, incident communication, scheduled maintenance, and subscriber notifications. Covers page configuration, component group management, incident lifecycle, metric tracking, and uptime reporting. Use when managing public or private status pages, communicating outages, scheduling maintenance, or reviewing component uptime in Atlassian Statuspage.

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

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.

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

Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

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

interview the user to design an agentic control loop (sensor, controller, actuator under disturbances) tailored to their codebase, then build it as locally-runnable components plus a scheduled coding-agent workflow

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