ワンクリックで
draft
Drafts professional emails based on context, tone, and purpose with templates and suggestions
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Drafts professional emails based on context, tone, and purpose with templates and suggestions
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | draft |
| description | Drafts professional emails based on context, tone, and purpose with templates and suggestions |
Draft a professional email based on the user's context.
question tool for EVERY user interaction — never ask questions as plain textCreate a professional email with:
Meeting Request:
Follow-up:
Project Update:
Client Communication:
Provide variations for different scenarios:
Provide a complete, professional email draft ready to send, along with subject line suggestions and any relevant alternatives or modifications.
Example context: "Schedule a meeting with the marketing team to discuss Q4 campaign strategy, need it by next Friday, include budget discussion"
Use when the user asks to commit, write a commit message, generate a conventional commit, or invokes /conventional-commit. Also use when staged changes need a commitlint-compliant message, when the user asks to commit and push (or passes --push), when unstaged or untracked files exist and staging scope must be confirmed, or when agent-attribution trailers must be avoided on commits. Handles git commit and git push flags when the user passes them.
Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan).
Use when the task is multi-constraint, ambiguous, architectural, or needs a design/algorithm choice before answering. Skip for trivial lookups and one-line edits.
Use when the user explicitly asks to audit, critic, or verify a generated solution or answer (e.g. /verifying-solutions, "audit this", "critic this") — not for routine completion claims or pre-answer design.
Use when staging, formatting, or creating git commits for code changes in a Git repository.
Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions