「status」の検索結果

Deprecated alias — use `/woz-kb <op>` (e.g. `/woz-kb status`).

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

Think and work like an expert Conservation Scientist. Use when a task calls for Conservation Scientist judgment. Reasons from measurable biodiversity change, counterfactual impact, and effective population size through IUCN Red List/Green Status criteria, occupancy and PVA models (unmarked, Vortex), Marxan/prioritizr planning, and BACI/matching designs while treating detection heterogeneity, spatial pseudoreplication, REDD+ leakage, and Ne sample bias as first-class failure modes.

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

Think and work like an expert Conservation Biologist. Use when a task calls for Conservation Biologist judgment. Reasons from IUCN Red List A–E and Green Status recovery metrics, PVA/Ne, occupancy and distance sampling (unmarked, msocc, RMark), prioritizr/Marxan SCP, Conservation Evidence and ROSES synthesis, counterfactual impact evaluation, METT/SMART PAME, and eDNA false-positive models while treating pseudoreplication, GBIF effort bias, offset baselines, and Red List≠priority conflation as first-class failure modes.

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

Medicines pipeline analysis over structured universes: Phase I-III assets with probability-of-success discipline (unadjusted peak x POS = modeled value; POS changes logged with reasons), trial status-diff tracking, and mechanism/competitor mapping via drug-knowledge lookups.

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

Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution, customising its embedded defaults for the team's product process. Use when setting up a new project, defining product standards, or when the user says 'set up requirement standards', 'define feature standards', 'configure requirement forge', 'define how features should be structured', or 'requirement forge refiner'.

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

Build and operate rights-aware Bria FIBO and FIBO Lite image-generation workflows with structured prompts, reference images, asynchronous status handling, webhooks, cost gates, and safe artifact downloads. Use when a user asks for Bria/FIBO generation, refinement, inspiration, reproducibility, hosted API integration, or a licensed-data image workflow; do not use for FIBO Edit, video, generic image editing, or third-party FIBO gateways.

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

Monitor any website for content changes, availability, performance, and security status. Combines page scraping, screenshot comparison, SSL monitoring, and security header checks for comprehensive website health and change detection.

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

Look up Common Vulnerabilities and Exposures (CVEs) with severity scores, affected software, exploitability status, and remediation guidance. Essential for security research, vulnerability management, and patch prioritization.

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

Enrich any company with comprehensive firmographic data including industry, size, revenue, funding, tech stack, beneficial ownership, and regulatory status. Combines multiple data sources for complete B2B company intelligence and due diligence.

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

Track flight status, delays, gate changes, and estimated arrival times for any commercial flight. Covers real-time flight tracking, schedule lookup, and delay monitoring for travel coordination and logistics planning.

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

cheat-on-skill 的陪跑进度 skill。用户问“今天该干嘛”“我现在做到哪了”“继续学”“打卡”“我卡住了”“下一步是什么”时触发。读取 .skill-state.json 的 active.progress 和 learning_plan，给当天任务、检查完成情况、记录进度、根据快慢调整计划。前置：已有 .skill-state.json 且 active.learning_plan 存在。

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

Internal — for Boundless team members only. Help developers deploy Boundless AWS infrastructure to the dev environment. Use when the user wants to deploy a service to dev, bootstrap their dev environment, troubleshoot infrastructure issues, or understand what env vars a service needs. Also handles teardown and status checks.

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

Internal — for Boundless team members only. Monitor Boundless deployment pipelines (AWS CodePipeline + CodeBuild) on the ops account. Use when the user wants to track a deployment after merging a PR, check whether a commit has rolled out to staging/prod, diagnose a failed deployment, watch the status of a specific pipeline, or get prompted to approve a production rollout once staging succeeds. Do NOT use for service runtime debugging (use ops-logs-query) or for deploying dev infrastructure (use ops-infra-deploy).

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

Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.

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

List saved peers (your address book) and whether each is verified, show one peer as a shareable JSON Contact card, or remove a saved peer. Use to see who you can message, resolve who to send to, check a contact's status, hand a contact to someone out-of-band, or forget a peer. `<user>` is this session's user directory (absolute path; from init).

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

Build customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Triggers on requests to build case studies, produce customer stories, create reference content, or when user asks "build a case study", "customer story", "reference account", "case study interview", "before/after story", "social proof page", "logo wall". Outputs CFD-CASE-* evidence entries, GTM-CASE-* marketing assets, and updates ADO-REF-* with story status.

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

Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary. Use standalone when CI is red, or as the check-fixing step invoked by /watch-pr. Repo is adamayoung/TMDb.

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

Build heads-up display (HUD) dashboards for AI coding agents — show context usage, active tools, running sub-agents, and task progress in real-time. Use when: monitoring AI agent activity, building developer tools for AI-assisted coding, creating status dashboards for agent workflows.

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

Verify meeting notes are fully processed. Args: <path>, [dates], all, pending [dates] [--step=X]. Shows which wrap steps are complete or missing.

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

Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.

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

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

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

Analyze GitHub and Discord signals to prioritize maintainer attention. Use when asked about priorities, what's hot, what needs attention, or project status.

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

Control CLAWDINATOR fleet lifecycle via the control API. Use for /fleet deploy or /fleet status.

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

Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and status updates.

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