「status」の検索結果

Show skill-bus overview, status, and available commands. Quick reference for all skill-bus features.

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

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.

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

Emulated Twilio REST APIs for local development and testing. Use when the user needs to test Twilio Messaging, Verify, Voice, phone numbers, webhooks, status callbacks, inbound SMS simulation, or Twilio SDK integrations without hitting the real Twilio service.

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

Operational workflow for hard integer-programming optimization tasks: selecting an installed solver, preserving solver/incumbent certificates, extracting feasible schedules, recomputing metrics from final outputs, and writing consistent reports. Use when a task requires a MIP, solver status, objective value, bound, gap, formulation write-up, or benchmark output files.

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

Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.

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

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

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

Prepare and manage durable MEX team handoffs in git-native project memory. Use when the user asks to hand work to a person or team, prepare an end-of-session handoff, save what the next engineer needs, create a MEX Relay, take or close a Relay, or invokes /mex-relay or $mex-relay. Keywords: mex, project memory, relay, handoff, team memory, Claude Code, Codex. Treat Relay as a memory baton, not chat, notifications, task assignment, issue tracking, or a Jira replacement; do not activate for ordinary status messages that are not durable handoffs.

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

Prepare and manage durable MEX team handoffs. Use when the user asks to hand work to a person or team, prepare an end-of-session handoff, save what the next engineer needs, create a MEX Relay, take or close a Relay, or explicitly invokes /mex-relay or $mex-relay. Treat Relay as a memory and context baton, not chat, notifications, task assignment, issue tracking, or a Jira replacement; do not activate for ordinary status messages that are not durable handoffs.

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

Display the current state of the FPF knowledge base

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

Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.

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

Prüft und entwirft AGB-Schiedsvereinbarungen nach Parteistatus, Form, Verfahrensbelastung und Auslandsbezug. Hält Hauptvertrag, Schiedsabrede und Vollstreckung auseinander; keine Abkürzung zur Umgehung zwingenden Verbraucherschutzes.

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

Worked qupai-system (曲牌体) opera scripts, act by act. Guan Hanqing's three surviving zaju (窦娥冤／救风尘／金线池 — twelve acts, 126 tunes, one mode and one rhyme per act, sung/spoken ratios); Tang Xianzu's 牡丹亭 (55 scenes, ~420 tunes, 集唐 closing quatrains, the 圆驾 south-north composite suite); Kong Shangren's 桃花扇 (44 scenes plus four unnumbered, the 副末 frame line, upper/lower halves, a fan's seven transformations, his sixteen 凡例); 长生殿 (Wang Jilie's fifty-scene staging table); Wei Minglun's 巴山秀才 (1983 Sichuan 高腔, 43 tunes, nine 帮腔 passages). Every case states its edition and collation status, then structure, tunes, stage conventions and transferable devices. Method is in sw-chinese-opera-qupai; this skill holds the worked scripts. Use when you want a real example of how a 传奇 or 杂剧 is assembled, need actual scene counts and tune counts to imitate, are judging where a famous script breaks prosody, or need models for 副末开场, 集唐下场诗, 南北合套 or 帮腔 (曲牌体全本／牡丹亭／桃花扇／窦娥冤／救风尘／长生殿／巴山秀才／唱段表／结构表).

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

AI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.

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

实操长片策划工作流（B站/YouTube 新赛道，实操+真人出镜）。产出可直接照着录的策划稿：测试题组（含可粘贴 prompt）、 结构时间轴（全身出镜段 vs PiP 段）、出镜口播稿、录屏操作清单、悬念与彩蛋设计。 Use when the user says 做实操长片, 实操视频, 实测视频, 对比实测, xx做成实操, 出个实测策划, 这个选题拍实操, or ra-选题 routes a 实操长片 立项 here. 策划稿落 `01-内容生产/视频工作台/制作中/<日期-主题>/策划稿.md`，frontmatter status 是与制作端交接的唯一状态机。

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

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

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

Research any company, product, or service from a URL plus description and build a comprehensive, evidence-bound AEO/GEO/AI-visibility prompt panel across buyer jobs, information acts, journey states, B0-B5 proximity, aided status, roles, locales, variants, partitions, surfaces, and measurement lanes. Use when a user wants prompts to track in ChatGPT, Claude, Gemini, Perplexity, AI search, or answer engines; wants an AI-visibility measurement design; or needs a versioned panel rather than an SEO keyword list.

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

Gate a prompt universe for schema and provenance completeness, target or campaign contamination, evidence entailment, naturalness, one-concept clarity, architecture consistency, aided status, answer leakage, and semantic duplicates. Use after realistic prompt generation and before human panel selection.

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

Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited canonical intent cells.

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

Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.

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

Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.

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

Shared backlog conventions for Azure DevOps, GitHub, and Jira. Use for platform resolution, autonomy tiers, sanitization guards, and story quality, and for Azure DevOps pull request creation and build status or log retrieval.

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

Jira issue workflows for search, issue updates, transitions, comments, field discovery, and interactive credential setup via the Jira REST API. Use when you need to configure Jira access, search with JQL, inspect an issue, create or update work items, move an issue between statuses, post comments, or discover required fields for issue creation.

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

Creates source-grounded internal or external weekly engagement status reports with optional Outlook draft creation.

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

Build a production behavior-tree runtime (Blackboard, action/condition leaves, sequence/selector/parallel composites, decorators) and a Utility AI system (response curves — linear, exponential, sigmoid, quadratic — considerations, and action evaluators), plus hybrid BT-drives-Utility agents. Use when implementing a reusable behavior-tree or utility-based decision system, or tuning enemy/NPC decisions beyond a simple FSM, or when the user mentions behavior tree, blackboard, decorator, selector, sequence, tick status, utility AI, response/scoring curve, or consideration. For choosing between FSM/BT/steering or for pathfinding, use game-ai; for Unreal's BehaviorTree/Blackboard assets, use unreal-behavior-trees.

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