「draft」の検索結果

Synthesises a batch of customer feedback (survey answers, reviews, ticket and chat comments) into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim quotes cited to record codes, contradictions and unverified claims, and the follow-up questions to answer next. Produces no sentiment score or percentage positive as fact; ratings appear only as distributions with n. Use when the user asks to "theme this feedback", "what are customers saying", "summarise these survey answers", "analyse these reviews", "find the top complaints in these comments" or "code this voice of the customer data". Do not use for exit interviews, use exit-interview-synthesis instead; for sorting a live queue and drafting replies, use ticket-triage-pack; for project retrospectives, use lessons-learned-synthesis. Drafts for human review; never approves, authorises or signs off.

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

Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).

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

Professional email drafting with appropriate tone and structure. Use when the user wants to write, compose, or draft an email.

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

Busabase-backed App-in-Skill CRM operator for contacts, companies, deals, and agent-drafted follow-ups in a reviewable follow-up queue. Use when the user invokes $kelly-crm or /kelly-crm, mentions CRM, pipeline, contacts, companies, deals, follow-ups, relationship management, meeting-note capture, outreach drafts, next steps, or wants to review/approve agent-drafted follow-up messages before they are sent through other channels.

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

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

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

Draft Stellar Community Fund Build Award applications interactively. Use when helping teams write their SCF submission — walks through project description, Stellar integration rationale, technical architecture, team section, deliverables, budget, and traction evidence. Produces a complete draft aligned with what funded projects look like.

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

Draft or review an employer's Otameshi Tenshoku listing so a candidate can decide whether to apply: check item by item that the work, deliverable, out-of-scope tasks, required experience, support, hours, schedule, location, compensation, contract form and payment timing are stated, find open-ended, unpaid-company-work, guarantee, personal-attribute and unverifiable wording, and confirm that the hours, weekly availability, period, rate and budget hold together. Use when a hiring manager, recruiter or small-business owner wants a listing written from a plan, wants an existing draft or published listing reviewed before or after posting, or wants to know why applications are not coming; do not use to design the work itself (trial-work-design), to reply to applicants (applicant-reply), to state market rates, legal, tax or service conditions from memory, or to post or update the listing on the user's behalf.

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

自动从知乎热榜选题、调用 AI 生成原创回答并保存为草稿，支持自定义话题关键词、写作风格和批量生成。 Draft Zhihu answers automatically: picks hot questions, generates original answers via AI, and saves them as drafts — with custom topic filters, writing style, and batch support. Never publishes.

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

Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.

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

Requires OFOX_API_KEY — create one at https://app.ofox.ai. Generate cheap vertical 9:16 drafts in one priced batch, pick a winner off the contact sheet, then re-render only that one. The cheap tier is the point — several times cheaper per second, so a whole set can cost less than one flagship clip. Use when a user wants Shorts/Reels/TikTok raw material rather than one finished video, e.g. "give me 5 vertical clips to choose from", "a few Reels drafts for this product", "some cheap options before we commit", or "batch me some 9:16 takes". Do not use when one finished clip is wanted — go straight to the scenario skill (seedance-ad-creative, ugc-ads, seedance-short-drama, seedance-product-video), which is also where this skill gets the prompt it drafts.

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

OpenClawのリリース情報を確認し、Discord向けの告知文を作成します。版ごとの更新手順や利用者に試してほしい点を整理し、投稿にも対応します。

• beta版の告知文を作りたいとき
• stable版の更新方法を案内したいとき
• 利用者向けのテスト項目の整理

Telegramの下書きと最終メッセージが届く順序を、OpenClawのQA Labで検証するスキル。QA Channelと実際のTelegramプラグインで同じシナリオを実行します。

• Telegramの下書きと最終配信を確認
• QA Channelで配信フローを検証
• 実際のTelegramプラグインで検証

ジョークの題材に合うミームのテンプレートを探し、文字入り画像の下書きを作るスキル。ローカルのSVG・PNG出力やImgflipでのURL発行に対応します。

• ジョークに合うミーム形式を選びたいとき
• 名前や話題からテンプレートを探す
• 文字入りSVG・PNGの下書き作成

Gitの変更内容と過去の履歴を確認し、Conventional Commitsの形式やリポジトリの慣例に沿って、種類・対象範囲・長さを整えたコミット文案を作るスキル。

• コミット前にメッセージを書きたいとき
• 既存のコミット文を確認・修正したいとき
• プルリクエストの短い要約作成

メモや調査資料をもとに、ブログ記事、ガイド、ニュースレターなどの長文を作成し、既存の文体やブランドの方針に合わせて構成と根拠を整えるスキル。

• メモや文字起こしを記事に仕上げたいとき
• ブランドの文体に合わせた記事作成
• 実用的なガイドやチュートリアルの執筆

AIへの依頼文から目的や不足情報を整理し、作業範囲に合うECCのコマンドやスキルを提案します。診断と改善理由を添え、そのまま貼り付けて使える依頼文に書き直します。

• 曖昧な開発依頼を具体化したいとき
• 依頼文に完了条件と検証を加えたいとき
• 作業に合うECCの構成を選びたいとき

営業・提携・資金調達の候補者を調べて優先順位を付け、共通の知人を通じた紹介経路を探し、相手の近況と送り手の文体に合わせてメールやSNSの連絡文を下書きします。

• 特定業界の見込み客を探したいとき
• 提携先や投資家候補の優先順位付け
• 共通の知人からの紹介経路の調査

記事やメモ、動画などをもとに、書き手の語り口を保ちながら、XやLinkedInの投稿、動画台本、ニュースレターを媒体に合う形で作るスキル。

• 一つの記事を複数媒体に展開したいとき
• 製品公開に向けた投稿の準備
• 短編動画やYouTubeの台本作成

複数のSNSに向けた投稿計画を作り、媒体ごとの文章や画像の要件、承認状況を整理します。公開確認や、予約投稿ツールへ渡す承認済み原稿の準備まで支援します。

• 翌月のSNS投稿を計画したいとき
• 新製品の発表を複数媒体へ展開
• 記事や動画をSNS投稿に再構成

会議メモや文字起こしから、根拠付きの決定事項と担当・期限を整理します。既存タスクとの重複を確認し、議事録、チケット、フォローアップ文面の下書きを作成します。

• 会議メモから作業を抽出したいとき
• 決定事項と担当・期限の確認
• 会議の約束と既存タスクの照合

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.

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

Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author. Use when the user asks for a beta read, beta readers, test readers, human review, reader review, to read something like a human, to be a first reader, whether a piece holds attention or will actually get read, for a quick read of whether a busy skimmer would even open a post, what readers will remember or take away tomorrow, where readers stop reading or bounce, or why a draft still feels off or hollow after anti-slop or humanizer edits. Final gate before publishing; reports where the reading broke; never rewrites.

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

Prioritize support requests, identify owners, route internally, and prepare safe customer drafts

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

Automate Draftable tasks via Rube MCP (Composio). Always search tools first for current schemas.

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