「lifecycle」の検索結果

When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.

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

Use when: ticket lifecycle, state transitions, ready for QA, changes requested, QA passed, role-based workflow policy, Developer to QA handoff, or relay routing across delivery agents.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

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

SSL/TLS certificate lifecycle management encompasses the full process of requesting, issuing, Dağıt:ing, monitoring, renewing, and revoking X.509 certificates. Poor certificate management is a leading

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

bu skill covers implementing Okta as a centralized identity provider for cloud environments, configuring SSO integration with AWS, Azure, and GCP, Dağıt:ing phishing- resistant MFA with Okta FastPass, managing lifecycle automation for user provisioning and deprovisioning, and enforcing adaptive access policies based on device posture and risk signals.

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

E-commerce product-management desk (Busabase App-in-Skill) for catalog master data, SKUs, pricing, inventory, channel status, content assets, compliance notes, lifecycle state, and approval-gated product operations. Use when the user invokes $kelly-products or /kelly-products, asks for 电商商品管理, 商品库, SKU 管理, inventory/reorder, product status across Amazon/Shopify/TikTok Shop/eBay, channel publishing approvals, price-change review, quality holds, product lifecycle/archive decisions, or a Busabase-backed product management desk.

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

Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel, retention, stickiness, or lifecycle metric.

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

Diagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty / 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A/A, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, and surprises after mid-run edits. Symptom-driven dispatch to the right diagnostic. TRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange / wrong / off, sees significance flipping, notices PostHog numbers disagreeing with their SQL, sees an A/A test showing significance, or reports surprises after mid-run edits. DO NOT TRIGGER when: creating a new experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).

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

Track ML experiments, manage model registry with versioning, deploy models to production, and reproduce experiments with MLflow - framework-agnostic ML lifecycle platform

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

Spawn, initialize, replace, transfer, and delete entities without breaking lifecycle, transforms, containers, or ownership.

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

Use when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. This should trigger for requests such as Review Java code for Quarkus application structure and CDI; Apply best practices for Quarkus configuration and beans; Improve CDI interceptors, events, or programmatic injection in Quarkus; Add virtual-thread configuration or tune CDI lifecycle. Part of cursor-rules-java project

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

NVIDIA DGX Spark User Guide リファレンス。GB10 Grace Blackwell Superchip ハードウェア仕様、first-boot / UEFI 設定、Spark Stacking クラスタ、 DGX OS / NGC / container runtime ソフトウェアスタック、 PXE / cloud-init プロビジョニング、fleet lifecycle 運用、 apt / fwupdmgr 更新、system recovery、PSIRT サポート、 vLLM / TensorRT-LLM / Ollama / ComfyUI / NIM / NeMo fine-tune / NCCL 等の build.nvidia.com/spark playbook、複数 Spark 接続・Tailscale・VS Code、 NVIDIA Developer Forums 由来の known issues / troubleshooting。

Push browser tab and download lifecycle events plus manager-owned background tabs. Read this when an agent needs lifecycle notifications or a temporary tab without polling.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

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

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

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

Design or review a declared control-command profile and its verb/backend lifecycle matrix. Distinguish policy denial, unsupported capability, delivery acknowledgement, independently observed effect, and unknown outcome; bind authorization to principal, target, scope, current policy, expiry, and fencing epoch. NOT for claiming runtime correctness, proving an adapter from declarations, or approving a control-panel button without independent runtime evidence.

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

Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.

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

OpenClawのプラグインを公開前に検証し、導入・削除、設定修復、起動、SDK互換性や配布パッケージの動作を確認して、結果と未検証項目を整理するスキル。

• 公開前に同梱プラグインの導入・削除を確かめたいとき
• ベータ版をクリーンな環境で検証したいとき
• 設定修復とgateway起動を確認したいとき

Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira/Linear/Taiga but needs structured delivery tracking.

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

製造現場の規格不適合について、対象品の隔離から原因分析、処置の検討、是正・予防措置の効果確認までを整理し、管理図の読み取りや仕入先品質の改善も支援します。

• 検査で見つかった不適合を調査したいとき
• 根本原因の分析手法を選びたいとき
• 是正措置の計画作成と効果確認

ECCを通じてNasiko CLIの導入状況を確認し、固定バージョンのインストールと管理対象の削除を、事前プレビューや利用者の同意を踏まえて進めるスキル。

• Nasiko CLIの導入状況を調べたいとき
• 検証済みバージョンの導入前確認
• ECC管理下のCLIを削除したいとき

ECCの導入・更新・再設定を、利用中のエージェント環境に合わせて進めます。導入状況の確認から変更内容のプレビュー、適用、検証までを対話形式で案内します。

• ECCを導入・更新したいとき
• Claude Codeで導入範囲を移したいとき
• Claude Codeでフックを調整したいとき

Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browser_use, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle hooks, MCP server setup, or monitoring/observability with Laminar or OpenLIT. Also trigger for questions about browser-use installation, prompting strategies, or sensitive data handling. Do NOT use this for Cloud API/SDK usage or pricing — use the cloud skill instead. Do NOT use this for directly automating a browser via CLI commands — use the browser-use skill instead.

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