「follow-up」の検索結果

This skill recommends follow-up morning cortisol and/or ACTH stimulation tests or insulin-induced hypoglycemia to assess HPA axis recovery in postoperative Cushing's syndrome patients with at least one intact adrenal gland. Triggers include postoperative remission (morning cortisol <5 µg/dL or UFC <28–56 nmol/d) and the need to evaluate HPA recovery before glucocorticoid discontinuation.

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

This skill recommends measuring late-night salivary or serum cortisol to screen for Cushing's disease recurrence in patients with eucortisolism after transsphenoidal surgery, including cases where eucortisolism was established by medical treatment prior to surgery. Use when postoperative follow-up shows eucortisolism (normal morning cortisol/UFC) but concern for recurrence exists.

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

This skill outlines monitoring glucocorticoid replacement in children with primary adrenal insufficiency (PAI) using clinical assessment of growth velocity, weight, blood pressure, and energy levels. Trigger when evaluating a child with PAI for adequacy of glucocorticoid therapy during routine follow-up.

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

Determines follow‑up interval for patients with primary adrenal insufficiency (PAI) based on age: annual visits for adults and children, and every 3–4 months for infants. Triggered when establishing routine endocrine care after PAI diagnosis or during stable management.

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

This skill guides annual evaluation of patients with primary adrenal insufficiency (PAI) for symptoms and signs of glucocorticoid and mineralocorticoid over- or under-replacement. Use during annual follow-up when assessing for weight changes, blood pressure abnormalities, edema, or symptoms such as fatigue, insomnia, or salt craving.

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

Generate conservative, editable English outreach drafts for foreign-trade sales from structured lead inputs and customer-intel signals. Use when an operator needs a first-touch or follow-up email draft that calls confirmed recent/customer-market signals from the customer-intel Skill, with subject options, review notes, and explicit reminders not to present unconfirmed facts as facts.

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

OpenClaw-native version of the foreign-trade outreach email skill. Use structured operator input plus customer-intel source context to generate conservative first-touch or follow-up email drafts without overstating inferred facts or inventing recent customer events.

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

Use when a foreign-trade operator already has a small customer list and needs conservative customer grouping, outreach angles, English subject lines, first-email drafts, follow-up cadence, and human review points before any sending happens.

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

Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add lifecycle hooks; transform agent configuration, environment, MCP servers, or workspace creation; automate permissions or turn follow-ups; add a native surface, sidebar item, or workspace panel; add Command Center items or slash commands; add composer pills or attachment sources; transform, render, or append agent timeline items; contribute a theme; use Paseo from plugin code; or add plugin RPCs.

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

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

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

Marketing operations manager handling budget planning, financial reporting, meeting preparation and follow-up, vendor management, and administrative workflows for marketing and communications departments. Designed for SME leaders who need to minimize time spent on operational overhead.

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

Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.

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

Remove Gemini AI watermarks from images using GeminiWatermarkTool (GWT). Use this skill whenever the user mentions: Gemini watermark, 浮水印, AI image cleanup, removing logos from Gemini-generated images, Google ImageFX cleanup, batch processing AI-generated photos, or anything about a semi-transparent logo in the bottom-right corner of an image — even if they don't say "GeminiWatermarkTool" explicitly. Also trigger for follow-up requests like "the corner still looks dirty" or "there's still residual artifacts" after a previous removal attempt.

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

Use after PROJECT_GUIDE.md exists, when the user asks if a project is worth their time, should they build vs buy, or invokes project-worth-my-time. Follow-up to explain-new-project—weighs project context (files, git history, chat) to recommend whether to invest in a repo, cherry-pick a feature, park the idea, pass, or use an existing polished product instead. Optionally enriched by a personal-memory MCP (e.g. Pieces) when one is available.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.

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

Update an existing GitHub Issue's description based on the issue number. Reads all issue comments and reflects any items not yet captured in the description. After refreshing the description, reviews it for remaining ambiguities or unclear requirements and posts any open questions as a follow-up 確認事項 comment.

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

Read and analyze Xiaohongshu comments from the user's signed-in Chrome session. Use to collect, export, summarize, or classify comments for content planning, follow-up posts, audience research, reply strategy, and 引流文案。

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

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

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

Rebase the branch past a merge so a follow-up PR carries only new work

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

Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.

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

Track vendor support tickets and RMA cases across multiple vendors. Use when managing support ticket lifecycle, updating ticket status from vendor emails, generating status reports, or identifying tickets needing follow-up.

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

Compose professional internal emails for coordination tasks like vendor quote requests, task delegation, and follow-up communications. Generates bilingual (JA/EN) email drafts with proper business tone. Use when user needs to draft internal emails for vendor RFQ forwarding, quote compilation requests, status updates, or task delegation.

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

Coordinate Codex work across the current task, internal subagents, user-owned tasks, worktrees, handoffs, formal review gates, or recurring automation. Use for delegation, parallel roles, another Codex task, cross-repo work, QA/review handoffs, scheduled follow-up, or task inspection and continuation. Chinese triggers include 子Agent/子进程/子对话, 另一个对话接手, 并行处理, 分给QA, 多仓库收口, 巡检, 持续推进, 定时自动继续, 创建/读取/转交任务.

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

Prepares a DRAFT vendor risk screening brief from the material the user provides on one vendor (questionnaire answers, certificates, assurance reports, policies, contract extracts): per screening topic, what a document evidences with reference, date and scope, what is only asserted, what is missing or contradicted, certificate and report details as stated, and ready-to-send questions for the vendor and the internal owners. No web research, no risk rating, tier, score or recommendation. Use when the user asks to "screen this vendor", "review the vendor's questionnaire answers", "check what the vendor's certificate covers", "what is missing from this due diligence pack" or "draft the follow-up questions for the vendor". Do not use for answering a customer's questionnaire about your own organisation, use vendor-security-questionnaire-prefill instead. Drafts for human review; never approves, authorises or signs off.

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