Claude Skill

email-writer

Write professional emails - commercial, administrative, follow-ups, difficult messages - with the right tone in FR/EN/AR. Use for any one-to-one email that matters.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_email-writer-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/email-writer
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Email Writer

Overview

A good email gets read, understood, and acted on. Subject decides open; first line decides read; clarity decides action.

Anatomy

  • Subject: specific, ≤7 words ("Proposition SAFA - v2 pour validation" > "Suite à notre échange")
  • Line 1: context or the point - never "J'espère que vous allez bien" alone
  • Body: one topic per email; bullets when >2 items; bold the ask
  • Close: explicit next step + deadline ("Pouvez-vous valider avant jeudi ?")
  • Length: 5-8 sentences for most business emails

Situational patterns

Situation Key move
Follow-up (no reply) add new value/info each time, never "je me permets de relancer" alone
Difficult message facts → impact → proposed path; no blame language
Request to a senior bottom line first, context after, easy yes/no
Administrative (FR) formal register, references (n° dossier), pièces jointes listed
Apology own it specifically, fix, prevention - no "sorry if"

Workflow

  1. Clarify: recipient, relationship, goal, language, urgency.
  2. Draft subject + email; match the register (tu/vous, titles in Gulf correspondence).
  3. One-read test: can the recipient act without re-reading?
  4. For sequences and mass sends, hand over to email-marketing / outreach-sequencer.

Rules

  • The ask appears once, clearly - not hidden in paragraph 3.
  • Sensitive emails (legal, firing, pricing) always get human validation before sending.
Files (navin)
  • SKILL.md 1.7 KB
    ---
    name: email-writer
    description: Write professional emails - commercial, administrative, follow-ups, difficult messages - with the right tone in FR/EN/AR. Use for any one-to-one email that matters.
    metadata: {"navin":{"emoji":"✉️","category":"writing"}}
    ---
    
    # Email Writer
    
    ## Overview
    
    A good email gets read, understood, and acted on. Subject decides open; first line decides read; clarity decides action.
    
    ## Anatomy
    
    - **Subject**: specific, ≤7 words ("Proposition SAFA - v2 pour validation" > "Suite à notre échange")
    - **Line 1**: context or the point - never "J'espère que vous allez bien" alone
    - **Body**: one topic per email; bullets when >2 items; bold the ask
    - **Close**: explicit next step + deadline ("Pouvez-vous valider avant jeudi ?")
    - **Length**: 5-8 sentences for most business emails
    
    ## Situational patterns
    
    | Situation | Key move |
    |-----------|----------|
    | Follow-up (no reply) | add new value/info each time, never "je me permets de relancer" alone |
    | Difficult message | facts → impact → proposed path; no blame language |
    | Request to a senior | bottom line first, context after, easy yes/no |
    | Administrative (FR) | formal register, references (n° dossier), pièces jointes listed |
    | Apology | own it specifically, fix, prevention - no "sorry if" |
    
    ## Workflow
    
    1. Clarify: recipient, relationship, goal, language, urgency.
    2. Draft subject + email; match the register (tu/vous, titles in Gulf correspondence).
    3. One-read test: can the recipient act without re-reading? 
    4. For sequences and mass sends, hand over to `email-marketing` / `outreach-sequencer`.
    
    ## Rules
    
    - The ask appears once, clearly - not hidden in paragraph 3.
    - Sensitive emails (legal, firing, pricing) always get human validation before sending.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related