Skip to main content
Business & Productivityreggiechan74

buildresume

Build a complete resume through all 3 steps (draft, provenance check, final)

Stars
19
Source
reggiechan74/JobOps
Updated
2026-05-29
Slug
reggiechan74--JobOps--buildresume
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/reggiechan74/JobOps/HEAD/plugins/jobops/skills/buildresume/SKILL.md -o .claude/skills/buildresume.md

Drops the SKILL.md into .claude/skills/buildresume.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Configuration

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).

Templates

For each template used by this skill, resolve the full path as:

{config.templates.base_dir}/{config.templates.active.}/

Templates referenced by this skill: evidence_verification_framework

Application Path Resolution

This skill writes to a per-application folder. Before writing any output:

  1. Parse {Company}_{Role}_{YYYYMMDD} from the job-posting filename, or honor --app=<slug> if supplied. The slug MUST be canonical: a leading PascalCase {Company} token (matching the Company_Intelligence/{Company}/ folder so OSINT links), a PascalCase {Role} (underscores between words allowed), and a trailing compact 8-digit date (20260519 — no hyphens, no time). Reject leading date/time prefixes such as 2026-04-15_214414_...; if the source filename carries one, recompose it into canonical form ({Company}_{Role}_{YYYYMMDD}) before composing the folder path.
  2. Compose the app folder: {config.directories.applications_root}/{app_slug}/.
  3. Resolve this skill's sub-folder by category:
    • resume-development (buildresume, provenance-check) → resume/
    • cover-letter (coverletter) → cover-letter/
    • rubric / assessment (createrubric, assessjob, assesscandidate, auditjobposting) → assessment/
    • briefing / interview prep (briefing, interviewprep) → interview/
  4. If the app folder does not exist, 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. Ensure the pinned copy begins with YAML front matter carrying output_type: job_posting: if the source JD already has a front-matter block, add the key to it; otherwise wrap a new block (--- / output_type: job_posting / source_jd: {filename} / ---) above the JD body.
  5. Exact-slug collisions (same Company+Role+Date) are not auto-suffixed. If the folder already contains the same output type, require the user to pass --app=<distinct-slug>.
  6. Output filenames (fixed; only the sub-folder above is resolved dynamically). Pass the fully resolved absolute path to each step's agent in its Task instruction:
    • Step 1 draft → resume/step1_draft.md
    • Step 2 provenance analysis → resume/step2_provenance.md
    • Step 3 final resume → resume/step3_final.md Any PDF/TeX/DOCX derivative shares the exact basename of its source .md and lives in the same sub-folder (e.g. resume/step3_final.pdf) — never a separate latex/ folder.

Arguments

  • $1: Job description file path (required)
  • $2: Cultural profile (optional, defaults to "Canadian")

Runs the three-step resume build sequentially:

  1. Step 1: Create initial tailored resume draft using HAM-Z methodology
  2. Step 2: Perform comprehensive provenance analysis for credibility
  3. Step 3: Create final hardened resume addressing all issues

Output metadata

Every markdown file generated during this skill must begin with a YAML front-matter block so downstream tooling can parse metadata without heuristics. Populate the fields with real values before writing any body content. The output path for each step is determined by step 6 of the Application Path Resolution protocol above (step 1 → resume/step1_draft.md, step 2 → resume/step2_provenance.md, step 3 → resume/step3_final.md); job_file in the front matter is always the absolute path to the input JD.

  • Step 1 draft — set generated_by: /buildresume step1-resume-draft, output_type: resume_step1, status: draft, version: 1.0.
  • Step 2 provenance analysis — set generated_by: /buildresume step2-provenance-check, output_type: resume_provenance, status: analysis.
  • Step 3 final resume — set generated_by: /buildresume step3-final-resume, output_type: resume_final, status: final. Increment version if regenerating after revisions.

Common fields for all three:

---
job_file: <absolute path to JD>
role: <target role title>
company: <hiring company>
candidate: <full candidate name>
generated_on: <ISO8601 timestamp>
---

Always write the front matter before any markdown headings or narrative body.

Step 1: Creating Initial Resume Draft

✓ Initiating strike package assembly

I'll start by reading the job description file and creating the initial draft using the $2 cultural profile.

First, let me read the job description:

@$1

Now I'll run the step1-resume-draft agent with the specified cultural profile:

✓ Deploying Step 1 Agent - Initial Draft Creation

I'm launching the step1-resume-draft agent to create an initial tailored resume draft based on the job requirements. This agent will:

  • Analyze the job requirements from $1
  • Apply the $2 cultural profile preferences
  • Use the HAM-Z methodology for strategic positioning
  • Review ALL education and credentials from master resume against job requirements
  • Explicitly justify any credential exclusions in agent output
  • Create a targeted first draft optimized for the role

I pass the resolved absolute output path ({app_slug}/resume/step1_draft.md, per step 6 of Application Path Resolution) to the agent in its Task instruction.

Step 2: Provenance Analysis

✓ Executing credibility verification sweep

✓ Deploying Step 2 Agent - Provenance Verification

Now I'll launch the step2-provenance-check agent to analyze the Step 1 draft for:

  • Credibility issues and evidence gaps
  • Risk factors for each major claim
  • Defensibility of quantified achievements
  • Consistency across all experience sections
  • Missing credentials: Verify ALL education/designations from master resume are evaluated
  • Credential-to-job mapping: Flag any excluded credentials that map to job requirements
  • Recommendations for strengthening credibility

I pass the Step 1 draft path ({app_slug}/resume/step1_draft.md) to read and the resolved output path ({app_slug}/resume/step2_provenance.md) to write, both in the agent's Task instruction.

Step 3: Final Hardened Resume

✓ Producing deployment-ready final resume

✓ Deploying Step 3 Agent - Hardened Resume Production

Finally, I'll launch the step3-final-resume agent to:

  • Incorporate all recommendations from Step 2 analysis
  • Address credibility concerns while maintaining competitive positioning
  • Produce a fully defensible final resume
  • Ensure maximum interview potential

I pass the Step 1 draft ({app_slug}/resume/step1_draft.md) and Step 2 provenance analysis ({app_slug}/resume/step2_provenance.md) paths to read and the resolved output path ({app_slug}/resume/step3_final.md) to write, all in the agent's Task instruction.

Mission Summary

All three steps of the resume assembly process will be completed:

  • Step 1: Initial targeted draft created
  • Step 2: Comprehensive provenance verification performed
  • Step 3: Final hardened resume produced

Your deployment-ready resume will be ready for mission execution with full credibility and competitive positioning.