メール、カレンダー、タスク管理、自動化（7,577 件）
概要と使いどころ
Compatibility skill for paywall upgrade cro. Use when a user or upstream workflow invokes this name; route the task to `paywalls` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for page cro. Use when a user or upstream workflow invokes this name; route the task to `cro` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for onboarding cro. Use when a user or upstream workflow invokes this name; route the task to `onboarding` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for geo prospect. Use when a user or upstream workflow invokes this name; route the task to `prospecting` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for geo schema. Use when a user or upstream workflow invokes this name; route the task to `schema` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for form cro. Use when a user or upstream workflow invokes this name; route the task to `cro` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Design lifecycle email programs and sequences with segmentation, deliverability, personalization, testing and measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for email sequence. Use when a user or upstream workflow invokes this name; route the task to `emails` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "build the email HTML", "make this email responsive", "fix dark-mode rendering", or "QA the email across clients"; produces the coded HTML build — a responsive table layout, dark-mode + accessibility pass, a client-render matrix, image-block fallbacks, and a plain-text parity check. Not for writing the copy — use email-creative-builder; not for scoring the email or computing EQS — use email-quality-auditor. 邮件HTML/响应式邮件/暗色模式渲染
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "write the email", "draft subject lines", or "build email creative"; produces the pre-click unit — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alt — message-matched to the destination page and claims-ledger-aware. Not for pre-scoring or ranking subject-line variants (spam/truncation/render pre-score) — use subject-line-lab; not for scoring the email or computing EQS — use email-quality-auditor; not for the multi-step flow — use email-sequence-designer; not for the A/B test plan — use send-experiment-designer. 邮件文案/主题行/邮件创意
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for competitor alternatives. Use when a user or upstream workflow invokes this name; route the task to `competitors` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Write B2B cold outreach and follow-up sequences grounded in relevance, evidence, concise value, compliant sending practices and clear calls to action.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor GitHub workflows, propose fixes for failures, and report status
日本語の概要は準備中です。原文の説明を表示しています。
Memory management and FreeRTOS context for the Megahub ESP32 project. Use when dealing with heap allocation, stack size, task creation, inter-task communication, semaphores, queues, or any ESP32 memory constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Detect review findings that belong in CI/lint/formatter rather than human review.
日本語の概要は準備中です。原文の説明を表示しています。
Riverbed Memory の suppression entry を活用するときの判断基準と CLI 操作を案内する。
パフォーマンス観点のレビューエージェント。 N+1クエリ、メモリ効率、キャッシュ戦略、可観測性の観点でコード変更を評価する。
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
日本語の概要は準備中です。原文の説明を表示しています。
Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Self-verification loop. After completing a task, re-read the original request, list each requirement, verify whether it was met, and fix gaps before stopping.
日本語の概要は準備中です。原文の説明を表示しています。
Run flowctl catalog status to check the control-plane state of an Estuary resource, or list catalog specs to see which connectors exist and which are active. Use when checking whether a task is running, disabled, or failing, interpreting status output, or enumerating connectors. Use when user says "check task status", "is my capture running", "catalog status", "flowctl catalog status", "what's wrong with my capture", "task failing", "check catalog status", "collection status", "derivation status", "why is my task disabled", "list my connectors", "show me my connectors", "list captures", "list materializations", "what connectors do I have", or "show me all my active connectors".
日本語の概要は準備中です。原文の説明を表示しています。