메뉴
Load when the user asks to draft, compose, or send an email — or to write a Telegram message that is substantively a message draft (not a quick reply).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Load when the user asks to queue, enqueue, or add a coding task to the fleet, dispatch a job to a repo, or ask the fleet worker to fix something. Trigger phrases: "add to fleet", "queue a job for", "send to fleet", "dispatch to".
Load when the user provides stock trading recommendations and wants positions sized and bracket orders placed on the Alpaca paper-trading account.
Load when the user wants to navigate a website, click through a flow, fill a form, extract data from a page, or record an interaction as a reusable playbook.
Load when the user asks to review code, audit a PR, find bugs in code they paste, or assess code quality. Trigger phrases: "review this", "look at my code", "is this right", "what's wrong with X".
Load when the user is responding to a customer inquiry, complaint, or support ticket and needs help drafting a reply with the right tone.
Load when the user wants analysis on a dataset — trends, distributions, summary statistics, or insights from a CSV/JSON/Excel file.
| name | Email Drafting |
| slug | email-drafting |
| description | Load when the user asks to draft, compose, or send an email — or to write a Telegram message that is substantively a message draft (not a quick reply). |
| icon | |
| color | #f59e0b |
| version | 1.1.0 |
| category | writing |
| tools | ["send_email","send_telegram_message"] |
| config_schema | {"type":"object","properties":{"tone":{"type":"string","enum":["formal","casual","persuasive","empathetic"],"default":"formal"},"signature":{"type":"string","default":""}}} |
Tone: {tone}. Signature: {signature}.
Subject lines must say what the email is about — not "Following up" or "Quick question".
Skip the "I hope this email finds you well" preamble unless the recipient relationship calls for it. Get to the ask in the first or second sentence.
One ask per email. If there are multiple, number them and put a deadline next to each that has one.
Always show the draft to the user before sending unless they explicitly said "send it".
