메뉴
Formatting conventions for email replies and forwards — quoting previous threads, attribution lines, and forward headers
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Helps users connect and use a service in Rebel when it isn't already in the built-in connector catalog. Acts as an expert advisor — runs the full build-vs-buy check (catalog, MCP Registry, community) before scaffolding a custom MCP server and guiding research, implementation, security review, and contribution.
Guides users through adding new tools or capabilities to an existing connector (MCP server). Handles eligibility, workspace setup, connector research, implementation via Software Engineer workflow, local testing, and PR submission with an extension-specific template.
Capture citable sources (meetings, documents, files, media, web content) as structured files in memory/sources/ with provenance metadata for traceability.
Help users celebrate impactful wins and surface important learnings by analyzing their recent communications and activities.
Guidelines for maintaining single sources of truth and using signposting to connect documentation without duplication
Evaluate a finalised meeting transcript and distribute relevant content to other spaces, deciding per space whether to copy the full transcript, write a sanitised summary, or skip.
| name | email-quoting |
| description | Formatting conventions for email replies and forwards — quoting previous threads, attribution lines, and forward headers |
| last_updated | "2026-03-25T00:00:00.000Z" |
| tools_required | [] |
| dependencies | [] |
| agent_type | main_agent |
When replying to or forwarding emails, always include the quoted previous thread in the body so recipients see full context. Threading headers (In-Reply-To, References, threadId) only group messages in some clients' threaded view — many recipients use non-threaded clients, see emails in notifications, or receive forwarded copies without the conversation history.
Before replying or forwarding, fetch the full conversation first (e.g., get_workspace_email_thread for Gmail).
Your new reply content here.
On Mon, Jan 6, 2026 at 10:00 AM, Alice <alice@example.com> wrote:
> Original message line 1
> Original message line 2
<p>Your new reply content here.</p>
<br>
<div>On Mon, Jan 6, 2026 at 10:00 AM, Alice <alice@example.com> wrote:</div>
<blockquote style="margin:0 0 0 0.8ex;border-left:1px solid #ccc;padding-left:1ex">
Original message line 1<br>
Original message line 2
</blockquote>
Your message about why you're forwarding.
---------- Forwarded message ----------
From: Alice <alice@example.com>
Date: Mon, Jan 6, 2026
Subject: Meeting Tomorrow
To: You <you@example.com>
Original message body here.
On DATE, SENDER wrote:)<blockquote> with conventional styling