From jobops
Generates strategic cover letters with requirements-matching tables from Step 3 resumes, job descriptions, and optional hiring manager names in jobops workspaces.
npx claudepluginhub reggiechan74/jobops --plugin jobopsThis skill uses the workspace's default tool permissions.
Read `.jobops/config.json`. If missing, stop with:
Writes tailored cover letters for job postings from URLs or recent jobs, using resume and profile data to highlight achievements. Saves as Markdown.
Generates personalized cover letters from resumes and job descriptions. Structures with hooks, qualification matches, gap addressing, and calls to action for job applications.
Tailors CV summaries and bullet points, analyzes job description gaps/keywords, and generates ATS-optimized cover letters for job applications.
Share bugs, ideas, or general feedback.
Read .jobops/config.json. If missing, stop with:
JOBOPS NOT CONFIGURED Run /jobops:setup to initialize your workspace.
Use config.directories.<key> for all file paths in this skill.
Use config.preferences.cultural_profile if this skill generates resume-style content.
Use config.preferences.default_jurisdiction if this skill has jurisdiction-sensitive logic (crisis/legal skills accept --jurisdiction=<ISO-3166-2> to override).
For each template used by this skill, resolve the full path as:
{config.templates.base_dir}/{config.templates.active.<template_name>}/
Templates referenced by this skill: candidate_profile_schema
This skill writes to a per-application folder. Before writing any output:
{Company}_{Role}_{YYYYMMDD} from the job-posting filename, or honor --app=<slug> if supplied.{config.directories.applications_root}/{app_slug}/.resume/cover-letter/assessment/interview/mkdir -p it, then copy
{config.directories.job_postings}/{filename} → {app_slug}/job_posting.md
so the pinned JD cannot silently change under completed work.--app=<distinct-slug>.$1: Step 3 final resume file path (required)$2: Job description file path (required)$3: Hiring manager name (optional, defaults to "Hiring Manager")Produces a compelling cover letter based on the validated Step 3 resume, featuring a strategic requirements-matching table that directly demonstrates fit for the role. Process:
First, let me read your Step 3 final resume:
@$1
Now loading the job description to extract critical requirements:
@$2
Running Step 4 Agent...
I'm launching the step4-cover-letter agent to create your cover letter. This agent will:
The cover letter will feature a two-column table that:
Your strategic cover letter will be saved as:
{applications_root}/{app_slug}/cover-letter/cover_letter.md
Before the letter content, write this YAML metadata block with actual values:
---
job_file: $2
role: <role title>
company: <company name>
candidate: <full candidate name>
generated_by: /coverletter
generated_on: <ISO8601 timestamp>
output_type: cover_letter
status: final
version: 1.0
---
Update timestamps and increment version on subsequent iterations.
The cover letter will:
After generation, you'll have:
The cover letter and resume work together as a cohesive application package, with every claim defensible and every achievement traceable to your comprehensive work history.