「live」の検索結果

AI โปรดิวเซอร์ไลฟ์สตรีม — overlay, scene setup, chat engagement, donation/subscription, sponsor integration สำหรับ Twitch/YouTube Live/TikTok Live/FB Live

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

Troubleshoot and debug LiveAvatar integration issues. Use when the user's LiveAvatar integration isn't working, the avatar is silent, audio is garbled, sessions fail to start, events aren't received, or they're getting API errors.

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

Use when the 文档/交付 role maintains client-facing project delivery document packages, especially Word/DOCX deliverables such as delivery lists, demo scripts, acceptance forms, change confirmations, quote notes, contract-adjacent materials, README/docs indexes, and internal handoff notes.

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

Implement, review, or improve Live Activities and Dynamic Island experiences in iOS apps using ActivityKit. Use when building real-time updating widgets for the Lock Screen and Dynamic Island — delivery tracking, sports scores, ride-sharing status, workout timers, media playback, or any time-sensitive information that updates in real time. Also use when working with ActivityKit, ActivityAttributes, Activity lifecycle (request/update/end), Dynamic Island layouts (compact/minimal/expanded), push-to-update Live Activities, or Lock Screen live widgets.

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

Set up automatic keepalive for Appwrite free-tier projects to prevent them from being paused after 7 days of inactivity. Use when working in a codebase that uses Appwrite, when the developer mentions Appwrite free tier, project pausing, or keeping an Appwrite project alive, or when you detect Appwrite configuration (node-appwrite dependency, APPWRITE_ env vars, Appwrite SDK imports).

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

Manage PostHog subscriptions — scheduled email, Slack, or webhook deliveries of insight or dashboard snapshots, optionally with an AI-written summary attached to each delivery. Use when the user wants to subscribe to an insight or dashboard, get an AI summary attached to those deliveries, check existing subscriptions, change delivery frequency, add or remove recipients, or stop receiving updates.

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

Extract proof-of-delivery number, recipient, delivery time, items, exceptions, and signature status from delivery receipts.

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

OpenClawの通常版とextended-stable版について、公開先、配布物の出所、テスト結果、Gatewayの実動作を照合し、リリース状況を確認します。

• stable版の公開完了を確認したいとき
• プラグインの配布漏れを確認したいとき
• extended-stable版の証拠確認

OpenClawのリリース候補に対するCIを実行・監視し、実際のプロバイダー接続やインストール・更新を検証して、失敗の原因と結果を整理するスキルです。

• OpenClawのリリース候補を検証したいとき
• 失敗したCIジョブの調査と再実行
• プロバイダーの認証と推論利用を確認

Telegramの下書きと最終メッセージが届く順序を、OpenClawのQA Labで検証するスキル。QA Channelと実際のTelegramプラグインで同じシナリオを実行します。

• Telegramの下書きと最終配信を確認
• QA Channelで配信フローを検証
• 実際のTelegramプラグインで検証

OpenClawのQAシナリオを模擬環境や実サービスで実行し、失敗原因の修正、結果レポートの確認、複数モデルの応答スタイル比較まで支援するスキル。

• 模擬環境や実サービスでQAを実行
• 失敗シナリオの原因調査と再検証
• 複数モデルのキャラクター比較

参考映像から測定した色やカットのリズムを使い、生成動画と既存映像を編集・合成して、数値で照合した完成動画と再編集用のタイムラインを作るスキル。

• 参考映像のスタイルで動画を作りたいとき
• 既存映像に生成クリップを追加したいとき
• 映像素材や3D小物の合成

複数のSNSへの投稿をSocialClawで予約・公開し、配信状況を確認します。画像などのアップロードや、複数媒体にまたがるキャンペーンの投稿予定の検証も扱います。

• 複数SNSのキャンペーン投稿予約
• 投稿用の画像などのアップロード
• 公開前に投稿予定を検証したいとき

候補の探索や比較を繰り返し、試行の根拠と判断を追記型の台帳に残すスキル。前回との整合性や再検証の結果を確認し、実取引や本番操作へ進む条件を明確にします。

• 試行を重ねて候補を比較したいとき
• 判断の根拠を記録したいとき
• 新情報で前回の採用候補を見直したいとき

顧客や取引先への返信案を人の承認に結び付け、承認された本文と送信先、送信結果を記録します。修正前の古い承認による送信や、複数の担当処理による重複送信を防ぐ設計です。

• 顧客への返信を承認制にしたいとき
• 承認本文と送信結果を記録したいとき
• 修正前の承認による送信を防ぎたいとき

Mailtrapで登録確認やパスワード再設定のメール送信を実装します。開発用のテスト環境と本番の送信先を分け、認証やドメイン確認、配信失敗への対処も整理します。

• 登録確認メールを追加したいとき
• パスワード再設定メールの実装
• 実際に配信せずテストしたいとき

QA the omo Senpi adapter (packages/omo-senpi, packages/senpi-task) against the REAL senpi binary in strict isolation, and write every artifact to the one canonical evidence path .omo/evidence/omo-senpi-adapter/<slug>/. The live drivers under packages/omo-senpi/scripts/qa/ create their own isolated SENPI_CODING_AGENT_DIR and ignore the caller's, so the real ~/.senpi/agent is never written. Ships scripts/resolve-evidence-dir.mjs, which is the ONLY sanctioned way to pick an evidence directory: it rejects traversal, separators, absolute paths, and stray roots such as local-ignore/qa-evidence. Use whenever someone changes anything under packages/omo-senpi or packages/senpi-task, or wants to QA, smoke-test, verify, or debug the Senpi adapter, the task/team engine, the DAG, task RPC, or skill delivery. Triggers: senpi qa, qa senpi, senpi-qa, test senpi adapter, verify senpi task, senpi task e2e, senpi team e2e, task dag qa, live senpi driver, senpi evidence path.

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

The shared Claude Docs viewer — an artifact TYPE. An artifact made from it is a doc: a live document that people and Claude read and edit together (people may also call it a page). The doc's content does not live in this artifact's files at all — it lives in the Claude Docs service and is read and written ONLY through the Claude Docs connector (its create, batch, read and update tools). Read this before touching such an artifact: it says what the files are, that an instance owns none of its own, how to change what the doc says (the connector, never a publish), and where a comment on the doc — including one sent to you from it — is read and answered (the connector's comment verbs; never these files, never the artifact's comment relay).

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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

Deploy and harden a Sliver C2 team server (BishopFox's Go-based adversary emulation framework) with multi-protocol listeners (mTLS, HTTP/S, DNS, WireGuard), redirectors, domain fronting, and multi-operator support for authorized red-team operations. Use when standing up resilient C2 for a red-team engagement or generating beacon/session implants that must survive blue-team detection.

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

Everything In Its Right Place. The universal post-work organizer. After any significant work session, EIIRP runs a 7-phase audit: (1) inventory every output, (2) walk taxonomy to decide where each lands, (3) check schema-pack consistency against the brain's actual shape, (4) file enriched brain pages, (5) audit the skill graph for DRY+MECE, (6) verify resolvability, (7) report. Named after the Radiohead song. Nothing produced during significant work lives only in chat — knowledge becomes permanent, patterns become reusable. Also carries the always-on auto-fire gate: when >=500 words of structured analysis on a user-shared document is about to be delivered, file the brain page first, then deliver the analysis with the link in that same reply.

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

When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).

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

Use when testing a local or public URL on a real device via BrowserStack, opening a live browser session on Android, iOS, or desktop browsers, or when the user mentions BrowserStack, real device testing, mobile testing, cross-browser testing, touch testing, or wants to verify behavior on a specific phone, tablet, or browser version. Also trigger when the user says "test this on Android/iPhone/Safari/Chrome mobile", asks to open a live session, or mentions demo-mobile.html, even if they don't mention BrowserStack by name.

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

Penetration test and red team report writing methodology. Covers executive summary structuring (risk-led narrative for non-technical readers), technical finding format (title, severity, affected scope, narrative, reproduction steps, impact, remediation, references), CVSS v3.1 / v4.0 scoring with vector justification, OWASP risk rating, evidence hygiene (redacting credentials, hashing client data, time-stamping every action), screenshot and PoC artifact management, finding chain narratives, scope/limitations/assumptions documentation, retest evidence and remediation tracking, deliverable formats (PDF, DOCX, HTML, JSON for SIEM ingestion), client-customer-deliverable separation, and common report mistakes (over-CVSSing, undermining the triager, missing the 'so what'). Use at the end of an engagement when authoring a deliverable, when restructuring a draft for executive readability, or when establishing a reusable report template for a consulting practice.

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