Claude
Skill
professional-writer
Write business letters, reports, memos, meeting notes, and formal documents in French, English, or Arabic. Use for any professional document that must be polished and correctly toned.
Virus-scanned
Reviewed automatically before listing.
Download
navinspire-ia-navin-navin_skills_professional-writer-e9c73a3.zip · 1 KB
Install
skills CLI
npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/professional-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
Professional Writer
Overview
Produce clean professional documents with the right register, structure, and cultural conventions for the audience.
Document types & structures
| Type | Structure |
|---|---|
| Formal letter (FR) | en-tête, objet, formule d'appel, corps, formule de politesse, signature |
| Business report | executive summary → context → findings → recommendations → annexes |
| Memo / note interne | objet, contexte en 2 lignes, décision/demande, prochaines étapes |
| Meeting minutes | participants, décisions, actions (owner + date), points ouverts |
| Executive brief | 1 page max: situation, options, recommandation |
Workflow
- Clarify: audience, goal (inform/convince/request), language, formality level, length.
- Outline first for anything > 1 page.
- Write with: short sentences, active voice, one idea per paragraph, concrete facts.
- Respect conventions: French formal letters keep classic politeness formulas; English business writing is more direct; Arabic follows regional register.
- Finish with
proofreaderpass; export viadocx-generator/pdf-generatorwhen a file is needed.
Rules
- Executive summary written last, placed first.
- Never bury the request - state it in the first third of the document.
- Numbers and names triple-checked; a typo in a name ruins a formal letter.
Files (navin)
-
SKILL.md 1.6 KB
--- name: professional-writer description: Write business letters, reports, memos, meeting notes, and formal documents in French, English, or Arabic. Use for any professional document that must be polished and correctly toned. metadata: {"navin":{"emoji":"🖋️","category":"writing"}} --- # Professional Writer ## Overview Produce clean professional documents with the right register, structure, and cultural conventions for the audience. ## Document types & structures | Type | Structure | |------|-----------| | Formal letter (FR) | en-tête, objet, formule d'appel, corps, formule de politesse, signature | | Business report | executive summary → context → findings → recommendations → annexes | | Memo / note interne | objet, contexte en 2 lignes, décision/demande, prochaines étapes | | Meeting minutes | participants, décisions, actions (owner + date), points ouverts | | Executive brief | 1 page max: situation, options, recommandation | ## Workflow 1. Clarify: audience, goal (inform/convince/request), language, formality level, length. 2. Outline first for anything > 1 page. 3. Write with: short sentences, active voice, one idea per paragraph, concrete facts. 4. Respect conventions: French formal letters keep classic politeness formulas; English business writing is more direct; Arabic follows regional register. 5. Finish with `proofreader` pass; export via `docx-generator` / `pdf-generator` when a file is needed. ## Rules - Executive summary written last, placed first. - Never bury the request - state it in the first third of the document. - Numbers and names triple-checked; a typo in a name ruins a formal letter.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.