Menú
Formatting conventions for email replies and forwards — quoting previous threads, attribution lines, and forward headers
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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.
Add, update, or remove connectors (MCP servers) in Rebel. Searches the built-in connector catalog first before suggesting custom builds. Handles setup, configuration, and security review for community connectors.
Capture citable sources (meetings, documents, files, media, web content) as structured files in memory/sources/ with provenance metadata for traceability.
Rules for writing error messages, toasts, banners, and recovery copy in Rebel's voice — dry, calm, helpful, and never apologetic. Use whenever you add or rewrite any user-facing error string.
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.
Help users celebrate impactful wins and surface important learnings by analyzing their recent communications and activities.
| 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