「status」の検索結果

Publish, deactivate, and delete AEM content programmatically via the Cloud Service Replication API (com.day.cq.replication). Covers single-path and bulk activation, preview-tier targeting with AgentFilter, synchronous/async options, ReplicationStatus checks, permission validation, workflow process steps, and replication event handling. Use when the user needs to publish pages, activate or deactivate content, check replication status, build workflow steps that replicate content, listen to replication events, query batch publication state, or work with Replicator, ReplicationOptions, or ReplicationStatusProvider in AEM Cloud Service.

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

Publish, deactivate, and delete AEM content programmatically via the Cloud Service Replication API (com.day.cq.replication). Covers single-path and bulk activation, preview-tier targeting with AgentFilter, synchronous/async options, ReplicationStatus checks, permission validation, workflow process steps, and replication event handling. Use when the user needs to publish pages, activate or deactivate content, check replication status, build workflow steps that replicate content, listen to replication events, query batch publication state, or work with Replicator, ReplicationOptions, or ReplicationStatusProvider in AEM Cloud Service.

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

Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).

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

Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.

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

FaceTimeの内部状態や発信準備を確認し、設定済みの所有者宛てに承認付きで音声・ビデオ通話を発信したり、通話の終了をリクエストしたりします。

• 通話の内部状態と発信準備の確認
• 設定済みの所有者へ音声通話したいとき
• 明示的にビデオ通話を頼みたいとき

Spotifyの曲検索や再生・一時停止、曲送りをターミナルから操作し、再生先デバイスの一覧確認や切り替え、現在の再生状況の確認まで行います。

• Spotifyで曲を検索したいとき
• 再生の一時停止や曲送りをしたいとき
• 再生先デバイスを確認・変更したいとき

BluesoundやNADのプレーヤーをコマンドで探し、再生・一時停止・停止や音量調整を行うスキル。機器のグループ管理とTuneInの検索・再生にも対応します。

• プレーヤーを探して状態を確認したいとき
• 再生操作と音量調整
• プレーヤーのグループへの追加・削除

ローカルネットワーク上のSonosスピーカーを探し、再生・停止・音量を操作します。複数台のグループ化や、お気に入り・再生キューの管理にも対応します。

• 部屋ごとの再生や音量を変えたいとき
• 複数のスピーカーをグループ化したいとき
• お気に入りや再生キューを操作したいとき

長期プロジェクトの既存文書を、規則・構造・現状・履歴の役割に整理します。エージェントの参照先と更新ルールを整え、文書のずれや削除したものの再作成を防ぐ運用を支援します。

• 散在するプロジェクト文書を整理したいとき
• セッション間で文脈を引き継ぎたいとき
• 意図的に削除した理由を残したいとき

DartとFlutterのコード作成・レビューで、状態管理、画面遷移、通信、例外処理、テストの実装パターンを参照し、アプリの構成を整えるスキル。

• 新機能の状態管理を選びたいとき
• null処理や非同期処理のレビュー
• ログイン状態で画面遷移したいとき

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

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

Retrieve live disruption status for the 13 monitored maritime chokepoints (Suez, Hormuz, Malacca, Bab el-Mandeb, Panama, and more). Use when the user asks whether a strait or canal is disrupted, congested, or safe for shipping right now.

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

Check server health, component status, and live metrics from the CLI. Run `health`, `health components`, and `health watch` for a real-time dashboard of circuit breakers and provider status.

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

Show federation health — peers, sessions, trust levels, and message metrics. Use when the user asks "is federation healthy?", "show peers", "federation status", or wants to inspect cross-installation agent connectivity.

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

Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation

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

Show MemPalace status — room counts, storage usage, and palace health.

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

Track multiple live deals with milestones, deadlines, action items, and status updates. Maintains a deal pipeline view and surfaces upcoming deadlines and overdue items. Use when managing a book of business, tracking process milestones, or preparing for weekly deal reviews. Triggers on "deal tracker", "deal status", "where are we on", "process update", "deal pipeline", or "weekly deal review".

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

Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live state, redeploys the same URL, and reports only the delta. For software projects whose workstreams are PRs, also read swe.md (the X.Y PR-numbering convention; pulling PR state with gh/git; a per-PR detail block). Needs the built-in Artifact tool (claude.ai login). Not for single-PR changes or public docs.

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

Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.

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

Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations. Use when the user runs /si:memory-status or asks how full or healthy the agent memory is.

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

Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.

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

Commit, push, branch, and manage version control with GitButler. Use for commits, selective dirty-file or hunk commits, branches, diffs, PRs, history edits, squashes, amends, undo, merge, apply, and unapply. For selected dirty files or hunks, inspect with `but diff`; use compact `but status` for commit order, branch/stack placement, or conflict overview; use `but status -fv` when file/hunk IDs or per-commit file details matter. Replaces git write commands.

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

Diagnose and mitigate GKE TPU or GPU nodes stuck in NotReady / NodeStatusUnknown ("Kubelet stopped posting node status") due to host kernel panics, hardware lockups, or disabled node auto-repair. Use when nodes stop heartbeating beyond the node auto-repair threshold and pods remain stuck in Terminating. Don't use for healthy nodes, pod-only application crashes, or routine GKE upgrades.

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

Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't use for pod-level application failures (use gke-workload-troubleshooting), autoscaler scale-up/scale-down decisions (use gke-cluster-autoscaler), or non-GKE compute.

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