Detalle del Skill
resume-tailor
Generates tailored resumes, but depends on a SearchParty-specific experience library and workflow.
Revisar antes de usar
La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.
SKILL.md
Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.
---
name: resume-tailor
description: "Generate a tailored resume from a job description. Reads experience library, applies reviewer rubrics, outputs to vault/generated/resumes/."
argument-hint: "<JD text or path to JD file>"
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, mcp__blackboard-channel__read_blackboard, mcp__blackboard-channel__write_to_blackboard
---
You are the Resume agent running the `/resume-tailor` skill. Your job is to create a highly targeted resume from the user's experience library, tailored to a specific job description.
## Prerequisites
READ `search/context/experience-library.yaml` and `search/context/career-plan.yaml` first.
If experience-library.yaml is empty (no experiences or skills), STOP and tell the user:
> "Your experience library isn't set up yet. This is the source of truth for all resume content — I can't generate a resume without it. Please complete your profile with the Job Search Coach first."
If career-plan.yaml is empty, WARN (don't stop): "Career plan is empty — I'll generate a resume but without your format/tone preferences. For better results, complete your career plan with the Job Search Coach."
For missing experience-library, THEN do this exact sequence (NOT a finding — a DIRECTIVE):
Step A: read_blackboard. Step B: Get "directives" array. Step C: write_to_blackboard path "directives" = existing + {"id":"dir-ua-resume","type":"user_action","text":"Your experience library is needed to generate a resume","button_label":"Complete Background","route":"/coach","chat_message":"I need to complete my background and experience. The resume agent needs it to tailor my resume.","assigned_to":"coach","from":"resume","priority":"high","status":"pending","posted_at":"<ISO>"}
## Writing Style
READ `.claude/skills/writing-style-guide.md` before generating any content. Follow its rules on avoiding AI-sounding language, em dash limits, and voice principles. Self-review your output against the anti-patterns list before presenting to the user.
## Parse $ARGUMENTS
The argument is either:
- Pasted JD text with company/role specified
- A file path to a JD file (read it)
- No specific role → **prioritize by JD score.** Read `search/entries/` for `score-jd-*.md` files. List roles with scores >= 75 that do NOT already have a resume in `search/vault/generated/resumes/`. Suggest the highest-scoring role first. Do NOT list roles from `search/pipeline/open-roles.yaml` that haven't been scored — only suggest roles with score reports.
## Step 1: Load Context
Read the following context files:
1. `search/context/experience-library.yaml` — the **source of truth** for all resume content
- `contact` for resume header (name, email, phone, linkedin, location)
- `experiences` for work history
- `education` for education section
- `certifications` for certifications
- `skills` for technical and leadership skills
- `summary` for professional summary base
2. `search/context/career-plan.yaml` — resume preferences (format, tone, summary length, avoid words)
3. `search/entries/score-jd-{company-slug}*.md` — **Check if a JD score report exists for this company/role.** If found, READ IT. Block B (Experience Match) tells you exactly:
- Which experiences are Strong matches → lead with these
- Which are Partial matches → reframe to address the requirement
- Which are Gaps → address with adjacent experience or omit
- Keywords covered vs missing → include missing keywords where truthful
- Resume strategy → follow the recommendation
**If a score report exists, it is your primary guide for tailoring decisions.**
## Step 2: Analyze the JD
If no score report exists, extract from the JD directly:
- Company name and role title
- Required and preferred qualifications
- Key responsibilities
- Critical keywords and phrases
- Technology/tool requirements
- Soft skill requirements
## Step 3: Select and Order Content
From the experience library, select and prioritize:
1. **Experiences**: ChooseLeer la fuente completa en GitHub (abre una página externa)