「follow-up」の検索結果

Prepare sales meetings from SDR replies, account dossiers, CRM notes, call notes, or transcripts. Produces account brief, buyer map, pain hypotheses, discovery questions, objection plan, meeting agenda, CRM handoff, follow-up email, and outcome memory. Use when "sales meeting prep", "prep this demo", "discovery call", "booked meeting", "SDR handoff", "post-call follow-up", "call notes", "sales transcript", or any request to prepare or follow up on sales development meetings.

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

Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.

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

Draft concise follow-up messages, nudges, reminders, and recap emails from open decisions, stale requests, or recent meetings. Use when the work is repetitive business writing with known context. Do not use for sensitive legal language, high-stakes negotiation, or board-level communication without review.

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

Continuously monitor a GitHub PR for merge conflicts, CI failures, and CodeRabbit review comments, then automatically fix any issues found. Polls every 5 minutes and loops until every check is green. Use this skill whenever a PR has just been created or code has been pushed to a PR branch — it should be the default follow-up action after any PR creation or push. Also trigger on: "watch this PR", "guard this PR", "monitor CI", "keep fixing until green", "PRを監視して", "CIが通るまで 直して", /pr-guardian. When a PostToolUse hook reports that a push or PR creation just happened, proactively invoke this skill to start monitoring without waiting for the user to ask.

Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/. For the promotion emails, see email-nurture. For the deck, see ppt-maker. For the social promotion plan, see social-calendar.

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

Generate non-binding follow-up action suggestions from lead summaries or lead lists. Use when users ask for next best actions, call list for hot leads, or follow-up draft plan without automatic execution. Recommended chain: summary-generator then action-suggester then supervisor approval. Do not use for parsing, storage, or autonomous action execution.

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

This skill suggests follow-up tests for specific comorbidities associated with Cushing's syndrome in patients with adrenal adenoma when CT density is less than 10 Hounsfield units. Use when managing a post-adrenalectomy Cushing's syndrome patient with confirmed adrenal adenoma pathology and low-density imaging (<10 HU).

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

This skill recommends lifelong follow-up tests for cardiac myxoma and associated disease (testicular tumors, acromegaly, thyroid lesions) in patients with Carney complex. Use when managing a Cushing’s syndrome patient with a confirmed or suspected Carney complex diagnosis (e.g., spotty skin lentigines, cardiac myxoma, endocrine tumors).

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

Track design iteration history and apply consistent styling decisions across revision cycles. Use when handling follow-up change requests that reference previous design decisions (e.g., '前回も色で良いんだけど', 'same style as before', 'like we discussed').

Internal audit support skill aligned with IIA (Institute of Internal Auditors) International Standards. Provides risk-based audit planning, audit program development, workpaper documentation, finding development (Condition/Criteria/Cause/Effect), and Corrective Action Request (CAR) tracking. Use when: planning annual/quarterly audits, creating risk assessment matrices, developing audit programs and test procedures, documenting audit workpapers, writing audit findings and reports, tracking corrective actions and follow-ups, preparing for external audits (SOX, ISO). Triggers: "internal audit", "audit plan", "audit program", "audit workpaper", "audit finding", "risk assessment", "CAR tracking", "corrective action", "IIA Standards", "COSO framework", "監査計画", "監査プログラム", "監査調書", "是正措置", "リスク評価".

Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

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

Capture decisions and commitments after a meeting and draft a concise follow-up.

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

Write the follow-up after a call in the owner's own voice instead of a bot template: recall the transcript, person card and full correspondence, extract agreements with an owner and due date, draft short and personal, show before/after against the old template, then send through the approval gate and file the result to the person card. Triggers: "/fa", "follow-up", "what should I write to <name> after the call", or a fresh call transcript landing in the vault.

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

Pull fresh follow-up call notes from a dedicated Telegram group into the CRM layer of a vault. Incremental and idempotent by message id, safe to re-run, and the manual counterpart of the weekly scheduled job. Triggers: "/faaa-sync", "pull the follow-up notes".

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

Personal App-in-Skill inbound-inquiry reception desk (Busabase App-in-Skill) for cross-border/foreign-trade sellers, aggregating WhatsApp, Instagram, Messenger, and email inquiries into a pipeline with a product knowledge base, quote worksheet, approval queue, and follow-up reminders. Use when the user invokes $kelly-inquiry or /kelly-inquiry, mentions 询盘, inquiry desk, WhatsApp leads, quote management, 报价, foreign trade sales, follow-up reminders, or a lead pipeline, wants inquiries triaged into new/replied/quoted/negotiating/won/lost stages, agent-drafted replies and quotes reviewed before sending, or stale deals surfaced.

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

Use this skill when managing post-SAP follow-up testing for a driver. Covers the testing cadence, recordkeeping, what happens if a test is missed, and how to transition the schedule to a new employer.

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

OpenClawのベータ版・安定版・長期保守版の準備、公開、復旧、検証を進めるスキル。承認済み修正の移植や検証記録、公開後の確認まで扱います。

• OpenClawのベータ版・安定版の準備
• 承認済み修正を長期保守版へ移したいとき
• 中断した公開を復旧したいとき

機能の実装後やマージ前に、別のエージェントへコードレビューを依頼します。変更内容と要件、対象のコミットを渡し、指摘の重要度に応じて修正を進めるスキルです。

• 大きな機能を実装した後のレビュー
• マージ前に変更を確認したいとき
• 複雑な不具合修正への第三者確認

GitHubやLinear、ローカルの通知を棚卸しし、重要度と担当者に応じた届け先を設計します。重複や不要な通知を整理し、次の対応が分かる運用にまとめるスキル。

• 複数ツールの通知をまとめたいとき
• CI失敗の重複通知を減らしたいとき
• 緊急通知とまとめ通知の振り分け

顧客の契約・請求状況を調べ、重複購入や更新失敗を分類し、返金・解約・請求管理画面の復旧から、顧客への返信案と製品の改善点まで整理するスキル。

• 重複契約や意図しない請求の調査
• 更新失敗や支払い方法の問題への対応
• 請求管理や解約画面を復旧したいとき

実際のメールボックスで受信メールの仕分け、返信の下書き、送信確認を進めるスキル。履歴と送信済みの記録を確かめ、使用アカウントや対応状況を明確にします。

• 受信箱の仕分けとアーカイブ候補整理
• 履歴を踏まえた返信を下書きしたいとき
• メールを送信して記録を確認したいとき

コード実装や不具合修正、PRレビューをBlackbox AIに委任します。複数モデルの結果を評価して選び、長時間の作業の監視や保存地点からの再開も扱うスキル。

• 機能実装や不具合修正の委任
• PRの不具合とセキュリティ確認
• 複数AIモデルの実装比較

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

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

Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.

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