메뉴
Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage Hope Agent application settings through conversation. Use when the user wants to view or change any app configuration: theme, language, proxy, temperature, notifications, tool timeout, context compaction, automatic session titles, web search, GitHub issue reporting, memory, embedding, multimodal embedding, dreaming (offline memory consolidation), recap, behavior awareness, smart-mode approvals, plan mode, ask-user-question timeout, tool-result disk spill threshold, embedded server, ACP control plane, MCP subsystem (kill switch / concurrency / backoff), per-skill env vars, or any other setting visible in the Settings UI. Trigger phrases: 'change settings', 'configure proxy', 'set theme to dark', 'turn off notifications', 'adjust temperature', 'show my settings', 'bind the server to all interfaces', 'enable smart mode', 'tune dreaming', 'disable mcp', 'show my channels'. Trigger even when the user doesn't explicitly say 'settings' — any intent to adjust app behavior qualifies.
Self-understanding and issue reporting for Hope Agent itself. Use when the user asks how Hope Agent works internally, asks about its own source code/docs/runtime behavior, reports a bug/failure/slowness/crash, asks to diagnose logs, or asks to create/submit a GitHub issue for a bug, feature request, or improvement (including when there is no bug). Chinese triggers: 自查, 了解自己, 自我诊断, 排查 Hope Agent, 提交 issue, 需求 issue, 功能改进.
Hope Agent browser automation — the standard `status → tabs → snapshot → act` loop, stale-ref recovery rules, and what to do when login / 2FA / captcha / camera-prompt / dialog blocks progress. Load this skill whenever you reach for the `browser` tool. Trigger on: user asks the agent to open / control / click / scrape / log into / verify something in a web app ('open X and click Y', '打开 X 然后点击 Y', 'log into my Gmail', 'scrape this page', 'fill out the form on X'); user reports a flow that requires real browser context (cookies, JS-rendered content, OAuth).
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger phrases: data stores, database path, sessions.db, memory.db, logs.db, background_jobs.db, knowledge index, where is data stored, query app data, 查数据库, 数据存储, 会话记录在哪, 记忆库在哪.
Self-service diagnostics — query Hope Agent's local SQLite databases (logs / sessions / background jobs) directly via the `exec` tool to investigate problems, analyze usage, and locate root causes. Trigger on: user reports something broken / failing / slow / stuck / not responding ('X 不工作', 'X 报错', 'X 卡住', '为什么 X 失败', 'why did X fail', 'show me the logs', 'check what happened'); ad-hoc data analysis ('this week's token usage', '最近调用最多的工具', 'how many subagent runs failed', 'tool error rate', 'find sessions where X happened'); verifying a fix ('did the error stop after I changed Y'). Use BEFORE asking the user to paste log snippets — the data is on disk, query it directly. Read-only — SELECT only, never UPDATE/DELETE/INSERT/DROP.
Working method for the Hope Agent knowledge space — how to capture, organize, link, retrieve, and maintain Markdown notes well with the `note_*` tools. Load whenever you are reading or writing notes in an attached knowledge base. Trigger on: user asks to take / save / organize / restructure notes, build or grow a knowledge base / vault / second brain, link related notes, find related or similar notes, distill a long note into atomic notes, build a map-of-content (MOC) / index, clean up broken links or orphans, or turn a conversation into a note. Chinese triggers: 记笔记, 整理笔记, 知识库, 知识空间, 笔记网络, 关联笔记, 拆成原子笔记, 建索引/MOC, 清理断链, 把对话存成笔记.
| name | email-draft |
| description | Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check. |
| version | 1.0.0 |
| author | Hope Agent |
| license | MIT |
| metadata | {"hermes":{"tags":["office","email","communication","writing","productivity"],"related_skills":["meeting-notes","status-report"]}} |
Trigger phrases: "draft an email", "reply to this email", "polish this email", "翻译这封邮件", "write an email to ".
Don't trigger for: chat messages, Slack DMs, in-app notifications, marketing copy. Those are different formats.
Always produce the draft in this layout. Use a fenced code block so the user can copy it cleanly:
Subject: <concise, action-oriented, ≤60 chars>
Hi <Name>,
<opening line — context or thanks>
<body — one focused paragraph per point, max 3 paragraphs>
<call to action / next step / explicit ask>
Best,
<Sender>
If the language isn't English, adapt greeting and sign-off to the local convention:
<Name>，你好 / 祝好，<Sender><Name>様 / よろしくお願いいたします。<Sender>Bonjour <Name>, / Cordialement, <Sender><Name>님께 / 감사합니다, <Sender>Clarify minimal essentials via ask_user_question if missing:
Subject line first — the subject is what gets read. Make it specific and action-oriented:
Body — three paragraph max:
Pre-Send Self-Check — after producing the draft, run through this checklist out loud (in your reply to the user, before the draft):
If any box fails, revise the draft before showing it.
Subject: 15 min on <topic>?
Hi <Name>,
I'm <role> at <company>. We're working on <one-sentence context>, and I noticed your work on <specific thing>.
Would you have 15 minutes in the next two weeks for a quick call? I'm happy to share <X> in return / send a written question if that's easier.
Either way, thanks for considering.
Best,
<Sender>
Subject: Re: <original subject>
Hi <Name>,
Thanks for thinking of me / sending this.
I've decided to pass for now because <one-sentence reason>. Specifically, <constraint>.
Happy to revisit if <condition>.
Best,
<Sender>
Subject: <Project> blocked on <decision>
Hi <Name>,
Quick heads-up: <project> is blocked on <specific decision> as of <when>.
Context: <2 sentences max — what's happening and what's at stake>.
I'd recommend <option>. Can you confirm by <date>, or shall we discuss live? Open to your input.
Thanks,
<Sender>
Subject: Re: <original subject>
Hi <Name>,
Thanks for the call/email. To make sure we're aligned:
- <decision 1>
- <decision 2>
Action items on my side:
1. <action> — by <date>
2. <action> — by <date>
Action items on your side:
1. <action> — by <date>
Let me know if I missed anything.
Best,
<Sender>
When the user asks to translate an email:
[note] comment outside the draft| Mistake | Fix |
|---|---|
| Generic subject ("Hi", "Followup") | Specific subject naming the topic + action |
| Burying the ask in paragraph 4 | Move to paragraph 1 or 2 |
| "Hope you're well" filler when familiar | Skip — go straight to topic |
| Vague deadline ("when you can") | Specific date or "no rush, just FYI" |
| Mixing 3 unrelated asks | Split into 3 emails |
| Auto-translation kept English greeting | Localize properly (你好, 안녕하세요) |