academic-letter-architect
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.
What this skill does
# Academic Letter Architect
## Table of Contents
- [Core Principles](#core-principles)
- [Workflow](#workflow)
- [Letter Structure](#letter-structure)
- [Tone and Language](#tone-and-language)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)
**Related skills (use instead for):**
- Personal statements: `career-document-architect`
- Cover letters to journals: `scientific-email-polishing`
- Grant proposals: `grant-proposal-assistant`
## Core Principles
**1. Show, don't tell**: Concrete examples beat adjectives
- ❌ "She is brilliant"
- ✅ "She independently developed a novel assay that our lab now uses routinely"
**2. Comparisons give context**: Readers need reference points
- ❌ "He is a strong student"
- ✅ "He is among the top 5% of graduate students I've mentored in 20 years"
**3. Enthusiasm is evidence**: Tone conveys conviction
- Lukewarm letters damage candidates
- Genuine enthusiasm must come through
**4. Address what matters**: Match content to opportunity
- Academic job: Research potential, teaching, mentorship
- Industry job: Practical skills, teamwork, adaptability
- Award: Specific achievements matching award criteria
## Workflow
Copy this checklist and track your progress:
```
Letter Architect Progress:
- [ ] Step 1: Gather context (candidate, opportunity, relationship)
- [ ] Step 2: Collect evidence (specific examples, achievements)
- [ ] Step 3: Draft opening (credibility, relationship, expectation)
- [ ] Step 4: Build body (evidence paragraphs, comparisons)
- [ ] Step 5: Craft closing (strong endorsement, availability)
- [ ] Step 6: Calibrate tone (enthusiasm level, superlatives)
- [ ] Step 7: Final polish (length, format, signature)
```
**Step 1: Gather Context**
Identify: Who is the candidate? What opportunity? Your relationship (advisor, collaborator, instructor)? How long have you known them? In what capacity? See [resources/methodology.md](resources/methodology.md#context-gathering) for information checklist.
**Step 2: Collect Evidence**
List 3-5 specific examples demonstrating excellence: Research achievements, intellectual contributions, professional qualities, overcoming challenges. Quantify where possible. See [resources/methodology.md](resources/methodology.md#evidence-collection) for evidence types.
**Step 3: Draft Opening**
Establish your credibility (position, experience). State relationship to candidate (role, duration, context). Set expectation (strong recommendation signal). See [resources/template.md](resources/template.md#opening-template) for opening structure.
**Step 4: Build Body**
Structure evidence into 2-4 paragraphs covering different dimensions (research, intellect, character). Include comparative statements ("top 5%", "best I've seen"). Connect evidence to opportunity requirements. See [resources/template.md](resources/template.md#body-structure) for paragraph templates.
**Step 5: Craft Closing**
Provide unambiguous endorsement statement. Offer availability for follow-up. Include professional signature with title/contact. See [resources/template.md](resources/template.md#closing-template) for closing structure.
**Step 6: Calibrate Tone**
Ensure enthusiasm matches actual assessment. Check superlative use (too many dilutes impact). Verify letter reads as advocacy, not obligation. See [resources/methodology.md](resources/methodology.md#tone-calibration) for calibration guide.
**Step 7: Final Polish**
Check length (typically 1-2 pages). Ensure formal formatting. Verify all specific claims are accurate. Validate using [resources/evaluators/rubric_academic_letter.json](resources/evaluators/rubric_academic_letter.json). **Minimum standard**: Average score ≥ 3.5.
## Letter Structure
### Opening Paragraph
**Purpose:** Establish credibility and relationship
```
Elements:
1. Your identity and position
2. How you know the candidate (role, context)
3. Duration of relationship
4. Capacity of observation (direct supervision, collaboration)
5. Clear statement of recommendation
```
**Example:**
"I am writing to provide my strongest recommendation for Dr. Jane Smith for the position of Assistant Professor. As the Director of the Structural Biology Center at X University, I have had the privilege of working closely with Jane for the past four years, first as her postdoctoral mentor and subsequently as a research collaborator. During this time, I have observed her exceptional scientific abilities, intellectual creativity, and professional maturity firsthand."
### Body Paragraphs
**Purpose:** Provide evidence-based assessment
**Paragraph 1: Research/Technical Excellence**
- Specific project achievements
- Technical skills demonstrated
- Independent thinking
- Problem-solving ability
- Publications/outputs
**Paragraph 2: Intellectual Contributions**
- Creativity and innovation
- Scientific insight
- Critical thinking
- Ability to ask important questions
- Conceptual contributions
**Paragraph 3: Professional Qualities**
- Work ethic and reliability
- Collaboration and teamwork
- Communication skills
- Mentorship of others
- Leadership potential
**Paragraph 4: Comparative Assessment**
- Direct comparison to peers
- Ranking in your experience
- Prediction of future success
### Closing Paragraph
**Purpose:** Summarize and endorse
```
Elements:
1. Overall assessment statement
2. Specific recommendation (enthusiastic, unambiguous)
3. Prediction for future success
4. Offer of availability for follow-up
5. Professional sign-off
```
**Example:**
"In summary, Jane is an outstanding scientist with exceptional research abilities, intellectual depth, and professional maturity. I give her my highest and most enthusiastic recommendation without reservation. She will make an excellent faculty member and I am confident she will develop an impactful, independent research program. Please do not hesitate to contact me if you require any additional information."
## Tone and Language
### Enthusiasm Levels
**Highest ("absolutely top"):**
- "My strongest possible recommendation"
- "Without reservation"
- "The best I have mentored in 20 years"
- "Truly exceptional"
**Strong ("top tier"):**
- "Highly recommend"
- "Outstanding"
- "Top 5-10% of students"
- "Excellent"
**Moderate ("good but not stellar"):**
- "I recommend"
- "Strong"
- "Above average"
- "Solid"
**Lukewarm (damaging):**
- "I am pleased to recommend"
- "Adequate"
- "Met expectations"
- "Did fine work"
### Comparative Statements
**Strong comparisons:**
- "Among the top 2-3 students I've trained in my career"
- "The most creative thinker I've mentored"
- "Will outperform 95% of candidates you consider"
- "Best [X] I've seen in [Y] years"
**Weak comparisons (avoid):**
- "One of our better students"
- "Above average"
- "Compares favorably to peers"
### Specificity Examples
| Vague (Weak) | Specific (Strong) |
|--------------|-------------------|
| "Productive researcher" | "Published 5 first-author papers including 2 in Nature journals" |
| "Good communicator" | "Regularly invited to present at lab meetings and gave a talk at the Gordon Conference" |
| "Works well with others" | "Mentored 3 undergraduate students, all of whom went to top graduate programs" |
| "Technically skilled" | "Independently established our lab's CRISPR screening platform" |
## Guardrails
**Key requirements:**
1. **Truthfulness**: Only write what you genuinely believe. Dishonest letters harm candidates and your reputation.
2. **Evidence-based**: Every claim should have a supporting example. "Smart" means nothing without evidence.
3. **Appropriate comparison**: Compare to relevant reference class (other postdocs, not all scientists ever).
4. **Match content to opportunity**: Emphasize research for academic jobs, practical skills for industry.
5. **Candidate voice preservation**: Reflect the candidate's actual achievements, not fabricated ones.
6. **Cultural awareness**: US letters are more superlative than other cultures. Calibrate appropriately.
**CommRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.