「stop」の検索結果

Operate HitKeep safely in isolated Git worktrees. Use when inspecting workspace state, resolving ports or URLs, starting or stopping development services, coordinating concurrent agents or QA runs, reusing active runs, reading bounded logs, or preparing a secret-free handoff.

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

Use when the user wants to turn a static scene, character images, aerial map, drawn path, or route-control image into an immersive first-person FPV AI video prompt, especially Seedance/Kling/Runway/Veo style one-shot videos with numbered stop markers, red-line path control, world-map flythroughs, camera route planning, variable character counts, non-human POVs such as drones, pets, robot vacuums, character references, timed interactions, dialogue, spatial audio, and negative constraints.

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

Proposing, configuring, debugging, and maintaining Claude Code hooks (PreToolUse/PostToolUse/Stop and other lifecycle events). Use for workflow automation or quality gates via hooks.

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

Set up Blender cameras with cinematic intent — focal length, depth of field (f-stop / focus object), composition (rule of thirds, leading lines), animated cameras (orbit, dolly, push-in), tracking constraints. Use whenever the user asks to "set up the camera", "frame the shot", "make it look cinematic / hero / portrait / wide-angle / telephoto", "add depth of field", "orbit the camera", or any composition/framing request. Make sure to use this skill even if the user does not say "camera" — also covers "hero shot", "close-up", "from above", "shallow focus", "85mm portrait look".

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

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

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

Design, prioritize and run measurable growth experiments across acquisition, activation, retention, referral and revenue. Use when a startup needs an experiment backlog, ICE/RICE prioritization, referral or UGC loops, rapid weekly testing, causal measurement, or stop conditions without spam, fake accounts or dark patterns.

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

Execute YAML test plan, stop on first failure, output rich debug prompt

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

Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.

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

Reference for Android VPN/proxy service lifecycle: runtime coordinators, status/telemetry flow, where to make changes. Use when touching service start/stop, handover, or coordinator code.

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

Kontextspezifische Marketinghypothesen entwickeln, vorprüfen und als messbare Experimente priorisieren. Nutze diesen Skill, wenn Ideen für Kanäle, Kampagnen, Angebote oder Wachstum gesucht werden, wenn eine Ideenliste auf Risiko und Machbarkeit geprüft werden soll, oder wenn aus Vorschlägen Experimentsteckbriefe mit Metrik, Laufzeit, Budget und Stopkriterium werden sollen. Sortiert vor der Bewertung aus, was rechtlich, plattformseitig oder finanziell nicht tragbar ist, und trennt Evidenz von Vermutung. Führt keine Kampagne aus und schaltet keine Anzeigen.

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

Use when the user asks Codex to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Codex Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.

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

Use when the user asks Claude Code to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Claude Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.

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

Evaluating online information for credibility, accuracy, and context. Covers the SIFT method (Stop, Investigate, Find, Trace), lateral reading, reverse image search, primary source verification, and common misinformation tactics. Use when assessing the trustworthiness of a web page, article, video, social media post, or any digital claim before relying on it or sharing it.

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

Token budget tracking and enforcement for Gastown convoy-level execution. Hard limits with pre-execution checking, per-convoy and per-agent tracking, structured stop reasons.

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

OpenStack Nova compute service skill for deploying, configuring, operating, and troubleshooting cloud compute infrastructure. Covers instance lifecycle management (create/stop/start/reboot/resize/migrate/evacuate), compute scheduling with filters and weights, flavor management, live migration procedures, hypervisor management (KVM/QEMU via libvirt), placement service for resource tracking, CPU pinning, NUMA topology, huge pages, cell mapping, VNC/SPICE console access, and capacity planning. Use when deploying compute via Kolla-Ansible, managing instances, debugging scheduler failures, or planning compute capacity.

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

3 秒钩子脚本：为电商短视频写前 3 秒开场（台词 + 画面 + 花字），按痛点/反差/结果先行/提问/数字/场景代入等钩子类型一次给出多版，并做合规自检。Use when the user asks for a hook, 开头, 黄金 3 秒, 前三秒, opening line, scroll-stopper, 完播率, or wants to rewrite a weak opening for 抖音 / TikTok Shop / 视频号 / Reels.

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

Set up and maintain Hierarchical Agent Memory (HAM) for Codex using scoped local memory files. Trigger on "go ham", "set up HAM", "ham commands", "ham help", "ham route", "ham remove", "ham update", "ham status", "ham benchmark", "ham baseline start", "ham baseline stop", "ham metrics clear", "HAM savings", "HAM stats", "HAM dashboard", "HAM sandwich", "HAM insights", "HAM carbon", or "HAM audit".

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

Set up Hierarchical Agent Memory (HAM) — scoped CLAUDE.md files per directory that reduce token spend. Trigger on "go ham", "set up HAM", "ham commands", "ham help", "ham route", "ham remove", "ham update", "ham status", "ham benchmark", "ham baseline start", "ham baseline stop", "ham metrics clear", "HAM savings", "HAM stats", "HAM dashboard", "HAM sandwich", "HAM insights", "HAM carbon", or "ham sync".

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

Use when claiming the AI bounty on the tDVV mainnet sidechain. This public claim skill now supports Portkey AA/CA only, requires CA sync and holder preflight before any write, and routes to AA/CA onboarding, AA/CA claim, or diagnostics-only stop handling.

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

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.

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

Use when starting, stopping, or checking the dot-dash live session dashboard — a real-time browser UI that monitors all active Claude Code sessions, streams transcripts, and supports prompt injection

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

Use when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing an item without completion under a required reason (duplicate, out of scope, superseded, wontfix, blocked), marking an item done with an evidence trail and required summary, or initializing GitHub tracking infrastructure for a project. Stops when the item already has a plan or is blocked on missing information.

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

Analyze live crypto K-line, price-volume, market-structure, and derivatives evidence, then turn it into a conditional trading plan with exact entry, invalidation, targets, position sizing, leverage, and three risk tiers. Use when a user wants both market analysis and an actionable risk-managed plan, asks whether or how to trade a coin, or requests entry/stop/target/size levels. Do not use for placing orders, managing an existing account, or guaranteeing returns.

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

Reviews a whole deliverable (talk, course module, paper, chapter, or referee report) against its manifest without rewriting it. Runs a deterministic gate for build, citations, numbers, facts, and leaks and stops on failure, then runs a finder over each section and a strong-model pass over the whole work, and adjudicates into checks/<date>/findings.json and report.md with anchored findings, severities, and honest NOT CHECKED coverage within a dollar budget. Use when asked to lint or review the whole talk, module, or paper, for a pre-ship review, or for the night shift. Revision stays serial and author-led.

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