「health」の検索結果

Use when a user asks to audit what recall fed agents. Not for source or remote-system changes.

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

Resolve `.mighty/loro/*.loro` merge conflicts safely using `mt merge`, then verify store health and sync.

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

Audit one bounded Proto UI deployment or publication evidence slice against an exact revision and delivery surface. Use to verify revision identity, environment result, artifacts, and observable health. Do not deploy, promote, roll back, publish, release, or change environment protection.

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

Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.

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

Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.

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

Use these skills to manage and monitor Oracle databases by executing SQL statements, exploring schema metadata, analyzing query performance, monitoring active sessions and resource consumption, and managing storage and object health.

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

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

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

Launches 5 parallel AI agents to produce a comprehensive restaurant audit with composite Restaurant Health Score (0-100), grade, and prioritized action plan

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

One-shot NowStack Mobile Android deployment with GPC Google Play Console CLI. Use when preparing Play Store releases, uploading AABs, syncing listings/screenshots, monitoring rollout health, or submitting Android without EAS Submit.

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

Head-to-Head Stock Comparison — compares two stocks across valuation, growth, profitability, financial health, technical setup, sentiment, and risk with category winners and a weighted overall score. Triggered by "trade compare <TICKER1> <TICKER2>".

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

Fundamental Analysis skill — valuation ratios, growth metrics, profitability, balance sheet health, competitive moat analysis, and management quality. Returns Fundamental Score (0-100). Triggered by "trade fundamental <TICKER>".

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

When mktg-studio is running on this machine, /cmo proactively narrates work into the dashboard via Bash + curl against the localhost HTTP API. Detect via /api/health, then log every meaningful action — the user sees what /cmo is doing in real time.

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

Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.

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

Review the operating health of a one-person company using lightweight metrics, bottleneck analysis, and stop-loss logic. Use when Codex needs to explain review concepts when needed, verify available outputs, ask one question at a time, present multiple bottleneck hypotheses, and write user-confirmed outputs into `opc-doc/`.

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

Perform a reflective consolidation pass over a hyalo-managed knowledgebase directory — detecting structural issues, fixing broken links, flagging stale content, normalizing metadata, and reporting what changed. Use this skill when the user says /hyalo-tidy, "consolidate the knowledgebase", "clean up the KB", "run KB hygiene", "tidy", or "what needs attention in the knowledgebase". Also use when the user asks about knowledgebase health, broken links, orphan files, stale iterations, or metadata inconsistencies.

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

Code quality dashboard. (gstack).

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

"Interpret macroeconomic indicators including GDP, inflation, unemployment, interest rates, and exchange rates to assess economic health and predict trends. Use this skill when the user needs to evaluate a country's economic outlook, understand monetary/fiscal policy impacts, or contextualize business decisions within the macroeconomic environment — even if they say 'is the economy doing well', 'what do rising interest rates mean for us', or 'explain today's economic data'.".

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

"Apply Moore's business ecosystem framework to analyze how firms co-evolve through four stages (birth, expansion, authority, renewal) and occupy different ecosystem roles. Use this skill when the user needs to map ecosystem dynamics in a platform or industry, evaluate keystone vs dominator strategies, assess ecosystem health, or when they ask 'what stage is this ecosystem in', 'how should we position in this ecosystem', or 'why is this ecosystem declining despite having a dominant player'.".

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

"Interpret the three core financial statements (income statement, balance sheet, cash flow statement) to assess business health and performance. Use this skill when the user needs to read financial statements, understand profitability vs cash flow, evaluate a company's financial position, or prepare for investor/board meetings — even if they say 'explain these financials', 'are we making money', 'read this annual report', or 'what do these numbers mean'.".

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

"Evaluate backlink quality using Domain Authority, Domain Rating, and trust metrics. Use this skill when the user needs to assess link profile health, identify toxic backlinks, or plan link building strategy — even if they say 'check my backlinks', 'link building', or 'domain authority analysis'.".

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

Check if a RIG preview deployment is actually running and healthy. Verifies CI triggered, images exist, pods started, and services respond. Use when a PR deployment seems broken or after pushing code.

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

Prepare customer or executive business reviews with outcome tracking, adoption health, ROI narrative, risks, commitments, and next-quarter plan using customer success and CX frameworks. Use when teams need QBRs, success plans, churn-risk conversations, or executive account reviews. Do not use for generic slide beautification or cold outreach prospecting.

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