Recommendation Letter Workflow
Use this skill for the full recommendation-letter pipeline: repository setup, dated folder naming, QMD drafting, description notes, and PDF rendering.
When To Use
- A new recommendation-letter repository needs to be created.
- An existing repository needs a new institution/application folder.
- A .qmd letter needs to be edited, rendered, or archived.
- Supporting application material needs to be turned into a referee letter or questionnaire answer.
Core Workflow
- Inspect the current repository state first.
- If starting fresh, create the standard folder structure from repository conventions.
- Name application folders
YYYY-MM-DD_institution/.
- Duplicate the template QMD into the new dated folder and tailor recipient details, date, and body text.
- Create a
description.qmd that records what was changed and why.
- Render with
quarto render <folder>/<file>.qmd.
- Check the PDF for placeholders, date accuracy, recipient accuracy, and layout issues.
Editing Rules
- Keep the repository organized around dated application folders plus a shared
template/.
- Use the repository's existing prose and formatting patterns unless the target institution requires a different tone.
- Replace institution-specific placeholders in both opening and closing paragraphs.
- Keep claims grounded in the applicant information already available in the repo.
- If a questionnaire is requested, answer directly in the same style as the letters and save the final text in Markdown.
Output Expectations
- For new work, create the repository structure, template, application folder,
qmd, and description.qmd.
- For existing work, update only the relevant dated folder and its rendered PDF.
- Prefer concise, reusable text that can be adapted across institutions without inventing new facts.
Additional Guidelines
For letter content quality standards (section limits, specificity rules, superlative caps, and formatting constraints), see editorial guidelines.
If You Need More Detail
See repository conventions for the exact folder layout, naming patterns, and template structure used in this repository.
1---2name: recommendation-letter-workflow3description: Use when creating or maintaining a repository of recommendation letters for applications, especially Quarto-based .qmd letters rendered to PDF. Use for bootstrapping a new repo, adding a new institution folder, editing an existing letter, or rendering final PDFs from application-specific materials.4---56# Recommendation Letter Workflow78Use this skill for the full recommendation-letter pipeline: repository setup, dated folder naming, QMD drafting, description notes, and PDF rendering.910## When To Use1112- A new recommendation-letter repository needs to be created.13- An existing repository needs a new institution/application folder.14- A .qmd letter needs to be edited, rendered, or archived.15- Supporting application material needs to be turned into a referee letter or questionnaire answer.1617## Core Workflow18191. Inspect the current repository state first.202. If starting fresh, create the standard folder structure from [repository conventions](references/repository-conventions.md).213. Name application folders `YYYY-MM-DD_institution/`.224. Duplicate the template QMD into the new dated folder and tailor recipient details, date, and body text.235. Create a `description.qmd` that records what was changed and why.246. Render with `quarto render <folder>/<file>.qmd`.257. Check the PDF for placeholders, date accuracy, recipient accuracy, and layout issues.2627## Editing Rules2829- Keep the repository organized around dated application folders plus a shared `template/`.30- Use the repository's existing prose and formatting patterns unless the target institution requires a different tone.31- Replace institution-specific placeholders in both opening and closing paragraphs.32- Keep claims grounded in the applicant information already available in the repo.33- If a questionnaire is requested, answer directly in the same style as the letters and save the final text in Markdown.3435## Output Expectations3637- For new work, create the repository structure, template, application folder, `qmd`, and `description.qmd`.38- For existing work, update only the relevant dated folder and its rendered PDF.39- Prefer concise, reusable text that can be adapted across institutions without inventing new facts.4041## Additional Guidelines4243For letter content quality standards (section limits, specificity rules, superlative caps, and formatting constraints), see [editorial guidelines](references/editorial-guidelines.md).4445## If You Need More Detail4647See [repository conventions](references/repository-conventions.md) for the exact folder layout, naming patterns, and template structure used in this repository.
wolf5996