Automated summary
Generates a professional, concise LaTeX cover letter based on the currently opened file context and available resume templates.
Strengths
- Automates personalized cover letter creation from a job description and existing resumes
- Uses LaTeX for a polished, professional output
- Asks the user for specific points to emphasize, tailoring the letter
Limitations
- Requires the active file to be named 'job_descriptions.md'
- Depends on resume templates in './Resumes/' directory
- LaTeX output may need separate compilation
When you have a job description file open and a LaTeX resume ready, and need a tailored cover letter quickly.
When no job description file is open or if you prefer manually writing the letter without format constraints.
Security analysis
SafeThe skill only reads files within the project (job description and resume templates) and writes a new .tex file. It uses safe tools (Read, Write, AskUserQuestion) and has no network access, code execution, or data exfiltration.
No concerns found
How this analysis is madeExamples
Generate a cover letter for this job description using my resume.Create a LaTeX cover letter based on the current job posting and my resume in ./Resumes/.name: cover-letter description: Generates a concise LaTeX cover letter based on the currently opened file context. allowed-tools: [Read, Write, AskUserQuestion]
Cover Letter Generator
This skill generates a professional, concise cover letter in LaTeX format based on the context from the currently opened file in the editor.
Instructions
When this skill is invoked:
-
Read the context: Look at the user's currently active file, the active file should be named as
job_descriptions.md. This file contains the company and job information that you will need to generate the cover-letter. -
Read resume templates: Look for the Resume files in
./Resumes/, glob them all, and:- Search for common resume file patterns:
*.tex - Read available resume templates to extract:
- Personal information (name, contact details, email, phone)
- Professional summary or objective
- Key skills and technical competencies
- Work experience and achievements
- Education background
- If multiple resume templates exist, prefer
.texfiles as they're easier to parse
- Search for common resume file patterns:
-
Gather additional information: Ask the user for:
- Company folder name (for organizing the output)
- Job ID or position identifier
- Any specific points they want to emphasize beyond what's in the resume
- Which skills or experiences to highlight for this particular position
-
Generate the cover letter:
- Keep it concise (aim for 3-4 paragraphs maximum), below 1 page.
- Use a professional tone
- Use the personal information extracted from the resume templates
- Highlight relevant skills and experience based on both the job context and resume
- Use the LaTeX
letterdocument class or a modern CV template format - Include standard sections: opening, body paragraphs, and closing
- Tailor the content to match the job description from the opened file
-
File naming: Save the cover letter as
{folder}-{jobID}-cv.texwhere:{folder}is the company/organization folder name provided by the user{jobID}is the job identifier provided by the user- Example:
acme-SWE2024-cv.tex - Save in the current working directory or a subdirectory specified by the user
-
LaTeX Format: Use a clean, professional LaTeX format. Include:
- Proper document class and packages
- Contact information header
- Date
- Recipient address (if available)
- Professional opening and closing
- Well-formatted paragraphs
Example Output Structure
\documentclass[11pt]{letter}
\usepackage[margin=1in]{geometry}
\usepackage{hyperref}
\signature{Your Name}
\address{Your Address \\ City, State ZIP \\ Email \\ Phone}
\begin{document}
\begin{letter}{Hiring Manager \\ Company Name \\ Company Address}
\opening{Dear Hiring Manager,}
[Concise paragraph expressing interest and highlighting key qualifications]
[Optional: Brief paragraph demonstrating knowledge of the company and fit]
[Closing paragraph with call to action]
\closing{Sincerely,}
\end{letter}
\end{document}
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/latex-cover-letter-generator-mmk3nicj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/latex-cover-letter-generator-mmk3nicj/download' --output '.skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md.part' && mv '.skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md.part' '.skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md' && test -s '.skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/cover-letter' && cp -R '.skill-downloads/latex-cover-letter-generator-mmk3nicj' '.claude/skills/cover-letter'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/latex-cover-letter-generator-mmk3nicj'openskills read 'latex-cover-letter-generator-mmk3nicj'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/latex-cover-letter-generator-mmk3nicj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Writing Fragments
Content
Mine raw writing fragments through a relentless interview, without imposing structure. Capture ideas, quotes, and leading words for later use.
UI Copywriting & Auditing
Content
Write or audit user-facing UI copy including buttons, errors, empty states, and tooltips across the monorepo, following the design system source of truth.
Music MIDI Extraction
Content
Extracts the MIDI or score from an existing music production via the CogMusic MCP tool and confirms availability.