What problem does it solve? Writing recommendation letters for fellowship, job, and school applications requires gathering verified facts about a person's role, accomplishments, and deadlines, then coordinating delivery — a process prone to unsupported claims, missing details, and missed deadlines. ## Core Features & Use Cases - Fact-grounded drafting: Verifies relationship, role, dates, program, deadline, recipient, and delivery channel before writing, and drafts only claims supported by permitted evidence. - Missing-information checklists: Asks targeted questions when facts are incomplete instead of fabricating content. - Request queue integration: Works from the Control UI's Logistics -> Recommendation Letters template, which stores schools, per-school deadlines with timezones, CV and Drive links, and per-project records. - Deadline awareness: A daily server-side pass emails the head professor about letter requests due within three days, computed from the request log. - Use Case: A lab member submits a letter request for three graduate schools; an admin uses this Skill to draft a letter grounded in the member's recorded project contributions, then hands the draft back in conversation for review. ## Quick Start Ask the assistant to draft a recommendation letter for a lab member applying to a specific program, providing the relationship, dates, and supporting accomplishments.
