Scientific Email Polishing

Composes and polishes professional scientific correspondence -- emails to collaborators, journal cover letters, and responses to peer reviewers -- ensuring clear communication, appropriate tone, explicit asks, and professional formatting for academic contexts. Use when writing or polishing scientific emails, cover letters to editors, reviewer responses, or when user mentions email to collaborator, cover letter to journal, reviewer response, or professional scientific correspondence.

200 stars 25 forksResearch & Science Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill scientific-email-polishing
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/scientific-email-polishing ~/.claude/skills/scientific-email-polishing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Scientific Email Polishing

## Table of Contents
- [Core Principles](#core-principles)
- [Workflow](#workflow)
- [Email Types](#email-types)
- [Tone Guidelines](#tone-guidelines)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

**Related skills for other document types:**
- Recommendation letters: `academic-letter-architect`
- Research statements: `career-document-architect`
- Grant proposals: `grant-proposal-assistant`

## Core Principles

**1. One email, one purpose**: Each email should have a clear, single objective

**2. Explicit asks**: State exactly what you need from the recipient and by when

**3. Context first**: Open with enough context for the reader to understand immediately

**4. Professional but warm**: Formal doesn't mean cold; collegial is appropriate

**5. Scannable format**: Busy recipients skim; use structure to aid quick reading

## Workflow

Copy this checklist and track your progress:

```
Email Polishing Progress:
- [ ] Step 1: Identify purpose and desired outcome
- [ ] Step 2: Draft subject line (clear, specific)
- [ ] Step 3: Write opening (context in first sentence)
- [ ] Step 4: Compose body (organized, scannable)
- [ ] Step 5: State explicit ask (what, by when)
- [ ] Step 6: Close professionally (next steps, sign-off)
- [ ] Step 7: Review tone (polite, appropriate)
```

**Step 1: Identify Purpose and Outcome**
Read the full skill on GitHub

Details

Skill name
scientific-email-polishing
Path
skills/scientific-email-polishing/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Scientific Email Polishing skill do?

Composes and polishes professional scientific correspondence -- emails to collaborators, journal cover letters, and responses to peer reviewers -- ensuring clear communication, appropriate tone, explicit asks, and professional formatting for academic contexts. Use when writing or polishing scientific emails, cover letters to editors, reviewer responses, or when user mentions email to collaborator, cover letter to journal, reviewer response, or professional scientific correspondence.

How do I install the Scientific Email Polishing skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Scientific Email Polishing popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Scientific Manuscript Review

200

lyndonkl/claude

Guides systematic multi-pass review and editing of scientific manuscripts (research articles, reviews, perspectives) to improve clarity, structure, scientific rigor, and reader comprehension. Use when reviewing or editing research manuscripts, journal articles, or perspectives, when user mentions manuscript, paper draft, article, research writing, journal submission, reviewer feedback, or needs to improve scientific writing.

Research & Science25

Scientific Clarity Checker

200

lyndonkl/claude

Reviews scientific documents for logical clarity, argument soundness, and rigor by auditing hypothesis-data alignment, claim-evidence chains, quantitative precision, hedging calibration, and terminology consistency across any document type. Use when reviewing scientific argumentation, checking claims vs evidence, auditing terminology, or when user mentions check clarity, review logic, scientific soundness, hypothesis-data alignment, or claims vs evidence.

Research & Science25

Score Intuition Density

200

lyndonkl/claude

Computes a 0-10 intuition-density score for a seed body using 8 concrete measurable signals — analogy presence, concrete worked example, counterfactual offered, reframe against default, biology-to-AI transfer, question posed, calibrated hedge, math-to-metaphor handoff. Emits both the numeric score and the list of triggered signals for auditability. Use after topic tagging to enrich seed frontmatter in the substacker Librarian pipeline. Trigger keywords — intuition density, score, signals, analogy count, worked example, density proxy.

Research & Science25

Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.