Initial commit
This commit is contained in:
322
skills/resume-writer/SKILL.md
Normal file
322
skills/resume-writer/SKILL.md
Normal file
@@ -0,0 +1,322 @@
|
|||||||
|
# Skill: resume-writer
|
||||||
|
|
||||||
|
AI-powered resume generation, improvement, and tailoring skill. Generates ATS-optimized, impact-focused resumes tailored to specific job descriptions.
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
|
||||||
|
Activate this skill when the user:
|
||||||
|
- Asks to generate, write, or create a resume
|
||||||
|
- Asks to improve, refine, or strengthen an existing resume
|
||||||
|
- Asks to tailor a resume for a specific job posting
|
||||||
|
- Asks to optimize a resume for ATS compliance
|
||||||
|
- Asks to convert a LinkedIn profile to resume format
|
||||||
|
- Mentions career scenarios: employment gaps, career changes, promotions, freelance work, military transition
|
||||||
|
|
||||||
|
## Input Gathering
|
||||||
|
|
||||||
|
Before generating any resume content, collect the following inputs. Use the user's existing resume file as the default source. Ask only for missing information.
|
||||||
|
|
||||||
|
### Required Inputs
|
||||||
|
|
||||||
|
| Input | Source | Fallback |
|
||||||
|
|-------|--------|----------|
|
||||||
|
| Current resume | Read existing file (e.g. `resume.md`) | Ask user to provide |
|
||||||
|
| Target job title | Ask user | Infer from resume |
|
||||||
|
| Industry | Ask user | Infer from resume |
|
||||||
|
| Seniority level | Ask user | Infer from resume titles |
|
||||||
|
|
||||||
|
### Optional Inputs (gather based on task)
|
||||||
|
|
||||||
|
| Input | When Needed |
|
||||||
|
|-------|-------------|
|
||||||
|
| Job description (URL or text) | Tailoring mode — fetch URL with webfetch tool |
|
||||||
|
| Key metrics/achievements | Bullet generation — ask user for numbers |
|
||||||
|
| Career scenario type | Scenario handlers — identify from context |
|
||||||
|
| Company type/size | Summary generation — ask user |
|
||||||
|
| Tone preference | Any task — default: confidently professional |
|
||||||
|
|
||||||
|
## Resume Generation Workflow
|
||||||
|
|
||||||
|
Follow these phases in order. Each phase produces output that feeds into the next. Iterate on each phase before moving forward.
|
||||||
|
|
||||||
|
### Phase 1: Professional Summary
|
||||||
|
|
||||||
|
Generate a 3-4 sentence professional summary. Select the appropriate template:
|
||||||
|
|
||||||
|
**Experienced Professional:**
|
||||||
|
```
|
||||||
|
Write a 3-4 sentence professional summary for a {JOB_TITLE} with {YEARS} years of experience in {INDUSTRY}. Key strengths include {SKILL_1}, {SKILL_2}, and {SKILL_3}. Most notable achievement: {BIGGEST_ACHIEVEMENT_WITH_NUMBERS}. Target role: {TARGET_JOB_TITLE} at a {COMPANY_TYPE}. Tone: confident and specific, not generic.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Career Change:**
|
||||||
|
```
|
||||||
|
Write a professional summary for someone transitioning from {CURRENT_ROLE} to {TARGET_ROLE}. Transferable skills: {SKILL_1_WITH_EXAMPLE}, {SKILL_2_WITH_EXAMPLE}, {SKILL_3_WITH_EXAMPLE}. Frame this transition as a strategic move. Highlight how background in {CURRENT_FIELD} gives a unique advantage in {TARGET_FIELD}. 3-4 sentences.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Executive:**
|
||||||
|
```
|
||||||
|
Write an executive-level professional summary for a {C_SUITE_VP_TITLE} with {YEARS} years of experience. Key metrics: {REVENUE_MANAGED, TEAM_SIZE, MARKET_EXPANSION}. Industries: {LIST}. Board or advisory experience: {IF_APPLICABLE}. Tone: strategic vision and proven impact — a leader, not an executor. 4-5 sentences maximum.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Entry-Level:**
|
||||||
|
```
|
||||||
|
Write a professional summary for a recent {DEGREE} graduate from {UNIVERSITY} seeking a {TARGET_ROLE}. Relevant experience: {INTERNSHIP_PROJECT_VOLUNTEER}. Key skills: {3-4_SKILLS}. Don't oversell or use language that implies years of experience not earned. Tone: enthusiastic and genuine, not desperate. 2-3 sentences.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Returning to Workforce:**
|
||||||
|
```
|
||||||
|
Write a professional summary for a {PREVIOUS_ROLE} returning to the workforce after {X} years. During the career break: {WHAT_DONE}. Before the break: {KEY_ACHIEVEMENT}. Target role: {TARGET_TITLE}. Frame the gap as context, not an apology. Focus forward on what is brought, not backward on what was missed. 3 sentences.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Phase 2: Bullet Point Generation
|
||||||
|
|
||||||
|
For each role in the work experience section, generate achievement-focused bullet points. Select the appropriate template:
|
||||||
|
|
||||||
|
**Achievement-Focused Bullets:**
|
||||||
|
```
|
||||||
|
Generate 4-6 achievement-focused resume bullet points for a {JOB_TITLE} at a {COMPANY_TYPE_SIZE}. Key responsibilities: {LIST_3-4}. Quantifiable results: {METRICS_AVAILABLE}. Each bullet: starts with a strong action verb, includes a measurable result, 1-2 lines long. Industry: {INDUSTRY}.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Duty-to-Achievement Transformation:**
|
||||||
|
```
|
||||||
|
Transform these duty-based descriptions into achievement-focused resume bullet points with quantified results:
|
||||||
|
{PASTE_DUTY_DESCRIPTIONS}
|
||||||
|
For each one, create a strong bullet point that demonstrates impact. If specific numbers aren't provided, use realistic placeholders marked with [X] to fill in.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Software Engineering Bullets:**
|
||||||
|
```
|
||||||
|
Write 4-6 resume bullet points for a {SENIORITY} Software Engineer. Tech stack: {TECHNOLOGIES}. Project types: {WORK_DESCRIPTION}. Team context: {TEAM_SIZE, TECH_LEAD, CROSS_FUNCTIONAL}. Focus on technical impact: performance improvements, reliability gains, delivery speed, system scale. Each bullet specific enough that a technical hiring manager would find it credible.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Leadership-Focused Bullets:**
|
||||||
|
```
|
||||||
|
Write 5 resume bullet points emphasizing leadership and management for a {TITLE} who managed {TEAM_SIZE} people. Key leadership achievements: {ACCOMPLISHMENTS_THROUGH_TEAM}. Include metrics around team growth, retention, performance improvement, or project delivery. Show leadership through strategy and people development, not just task management.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Quantification Helper:**
|
||||||
|
```
|
||||||
|
Here are resume bullet points that lack quantification. Add realistic, specific numbers to each one. If estimation is needed, use ranges or realistic placeholders:
|
||||||
|
{PASTE_BULLETS}
|
||||||
|
For each, provide the improved version with numbers and briefly explain what metric to track.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Phase 3: Skills Section
|
||||||
|
|
||||||
|
Generate an optimized skills section:
|
||||||
|
|
||||||
|
**Job Description Match:**
|
||||||
|
```
|
||||||
|
Based on this job description, generate an optimized skills section. Include both hard skills and soft skills, organized into categories. Prioritize skills from the job description while including related skills. Job description: {PASTE_JD}. Current skills: {PASTE_SKILLS}. Show which skills to add, keep, and which are less relevant.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Technical Categorization:**
|
||||||
|
```
|
||||||
|
Organize these technical skills into a clean, well-categorized skills section for a {JOB_TITLE} resume: {PASTE_SKILLS}. Create categories like 'Languages', 'Frameworks', 'Tools', 'Cloud/Infrastructure', 'Methodologies'. Put the most relevant skills for {TARGET_ROLE} first within each category. Suggest any commonly expected skills that might be missing.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Soft Skills Reframing:**
|
||||||
|
```
|
||||||
|
Rewrite these generic soft skills as specific, professional competencies that sound credible on a resume:
|
||||||
|
{PASTE_SOFT_SKILLS}
|
||||||
|
For each, provide a more specific, professional-sounding alternative that implies the same quality.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Phase 4: ATS Optimization
|
||||||
|
|
||||||
|
Perform ATS optimization when a job description is available:
|
||||||
|
|
||||||
|
**Keyword Integration:**
|
||||||
|
```
|
||||||
|
Here's a job description: {PASTE_JD}. Here's my resume: {PASTE_RESUME}. Identify the top 15 keywords and phrases from the job description that should appear in the resume. For each keyword: (1) whether it's already in the resume, (2) if not, suggest where and how to add it naturally — as part of an achievement bullet, not just stuffed into a skills list.
|
||||||
|
```
|
||||||
|
|
||||||
|
**Section Heading Audit:**
|
||||||
|
```
|
||||||
|
Review resume section headings for ATS compatibility. Current headings: {LIST_HEADINGS}. Flag any that might confuse an ATS parser and suggest standard alternatives. Check whether any sections that ATS platforms commonly look for are missing (Summary, Skills, Certifications, etc.).
|
||||||
|
```
|
||||||
|
|
||||||
|
**ATS Formatting Rules (always apply):**
|
||||||
|
- Use standard section headings: Summary, Skills, Experience, Education, Certifications
|
||||||
|
- No columns, tables, headers/footers, or images in markdown output
|
||||||
|
- Spell out acronyms on first use: "Application Tracking System (ATS)"
|
||||||
|
- Use bullet points (not paragraphs) for experience
|
||||||
|
- Include full dates with month and year
|
||||||
|
- Place key keywords in context within bullet points, not just in a skills list
|
||||||
|
- Avoid special characters that ATS parsers may not handle
|
||||||
|
|
||||||
|
### Phase 5: Job Tailoring
|
||||||
|
|
||||||
|
Tailor the resume to a specific job description. If the user provides a URL, fetch it with the webfetch tool first.
|
||||||
|
|
||||||
|
**Gap Analysis:**
|
||||||
|
```
|
||||||
|
Compare my resume content to this job description and identify: (1) Keywords and skills from the job description missing from the resume, (2) Experience that aligns but uses different terminology, (3) Specific suggestions for how to adjust the resume to better match this role. Be specific — tell exactly which keywords and where to add them.
|
||||||
|
Resume: {PASTE_RESUME}
|
||||||
|
Job description: {PASTE_JD}
|
||||||
|
```
|
||||||
|
|
||||||
|
**Bullet Point Tailoring:**
|
||||||
|
```
|
||||||
|
Rewrite these resume bullet points to better align with a {TARGET_JOB_TITLE} position. The job description emphasizes: {LIST_3-4_KEY_REQUIREMENTS}. Keep the underlying achievements the same (don't fabricate), but adjust the emphasis, terminology, and framing to match what this specific role values.
|
||||||
|
Current bullets:
|
||||||
|
{PASTE_BULLETS}
|
||||||
|
```
|
||||||
|
|
||||||
|
**Cross-Industry Translation:**
|
||||||
|
```
|
||||||
|
Moving from {CURRENT_INDUSTRY} to {TARGET_INDUSTRY}. Translate these achievements into language that resonates with {TARGET_INDUSTRY} hiring managers:
|
||||||
|
{ACHIEVEMENTS}
|
||||||
|
Use terminology common in {TARGET_INDUSTRY}, highlight transferable skills, and frame achievements in terms of impact metrics that {TARGET_INDUSTRY} cares about.
|
||||||
|
```
|
||||||
|
|
||||||
|
## Scenario Handlers
|
||||||
|
|
||||||
|
### Employment Gap
|
||||||
|
```
|
||||||
|
I have a {X}-month/year employment gap from {DATE} to {DATE} due to {REASON}. Write a brief, honest explanation (2-3 sentences) to include in the resume or cover letter that acknowledges the gap without being apologetic. Frame it as a period of {growth/purpose/transition} and pivot immediately to what is being brought forward.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Internal Promotions
|
||||||
|
```
|
||||||
|
Write resume entries for progressive roles at the same company: {ROLE_1, DATES} → {ROLE_2, DATES} → {ROLE_3, DATES} at {COMPANY}. Show clear career progression and increasing scope. Each role: 3-4 bullet points. Most recent role gets the most detail. Show growth in: {AREAS_OF_GROWTH}.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Freelance/Contract Work
|
||||||
|
```
|
||||||
|
Format freelance experience for a resume targeting full-time {TARGET_ROLE} positions. Freelanced as a {FREELANCE_TITLE} for {X} years, working with clients including {NOTABLE_CLIENTS}. Key projects: {2-3_PROJECTS}. Present this emphasizing consistency, professionalism, and results — not as scattered gig work. Use a format that a hiring manager at a traditional company would respect.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Short Tenure / Job Hopping
|
||||||
|
```
|
||||||
|
Several roles with short tenures (6-12 months each). Help present these on a resume minimizing the appearance of job hopping. Roles: {LIST_ROLES_WITH_DATES_AND_REASONS}. Options: grouping similar roles, emphasizing impact over duration, or using a functional hybrid format. Suggest the best approach and write the resume entries.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Military to Civilian
|
||||||
|
```
|
||||||
|
Translate military experience into civilian resume language for a {TARGET_ROLE}. Military background: {RANK, BRANCH, SPECIALIZATION, YEARS}. Key achievements: {MILITARY_ACCOMPLISHMENTS}. Don't use military jargon — translate everything into business-world terminology. Frame leadership, logistics, operations, and training experience in terms civilian hiring managers understand.
|
||||||
|
```
|
||||||
|
|
||||||
|
## Improvement Tools
|
||||||
|
|
||||||
|
Use these when the user asks to improve, refine, or strengthen an existing resume.
|
||||||
|
|
||||||
|
### Weak Bullet Strengthener
|
||||||
|
```
|
||||||
|
These resume bullet points are weak. Rewrite each to be more impactful: start with a strong action verb, include a quantified result, and be specific about the achievement:
|
||||||
|
{PASTE_WEAK_BULLETS}
|
||||||
|
```
|
||||||
|
|
||||||
|
### Action Verb Upgrade
|
||||||
|
```
|
||||||
|
Replace the weak or overused action verbs in these bullet points with stronger, more specific alternatives. Don't use 'spearheaded,' 'leveraged,' or 'utilized' — those are overused in AI-generated resumes. Choose verbs that precisely describe what was done:
|
||||||
|
{PASTE_BULLETS_WITH_WEAK_VERBS}
|
||||||
|
```
|
||||||
|
|
||||||
|
**Strong action verb reference by category:**
|
||||||
|
|
||||||
|
| Category | Verbs |
|
||||||
|
|----------|-------|
|
||||||
|
| Leadership | Directed, Orchestrated, Championed, Steered, Mobilized |
|
||||||
|
| Creation | Architected, Designed, Engineered, Built, Pioneered |
|
||||||
|
| Improvement | Optimized, Accelerated, Streamlined, Overhauled, Elevated |
|
||||||
|
| Analysis | Diagnosed, Evaluated, Assessed, Validated, Investigated |
|
||||||
|
| Growth | Scaled, Expanded, Amplified, Grew, Multiplied |
|
||||||
|
| Delivery | Shipped, Launched, Deployed, Executed, Delivered |
|
||||||
|
| Reduction | Slashed, Trimmed, Curtailed, Minimized, Consolidated |
|
||||||
|
| Collaboration | Partnered, Coordinated, Unified, Integrated, Aligned |
|
||||||
|
|
||||||
|
### Full Resume Critique
|
||||||
|
```
|
||||||
|
Critically review this resume as if you were a hiring manager for a {TARGET_ROLE} position. Be brutally honest about: (1) which bullet points are weakest and why, (2) what's missing that a hiring manager would expect, (3) what should be cut or condensed, (4) whether the overall narrative is compelling. Provide specific, actionable suggestions.
|
||||||
|
{PASTE_RESUME}
|
||||||
|
```
|
||||||
|
|
||||||
|
### Tone Adjustment
|
||||||
|
```
|
||||||
|
Adjust the tone of these resume bullet points from {CURRENT_TONE} to {TARGET_TONE}. Keep the same achievements and metrics, just change how they're communicated:
|
||||||
|
{PASTE_BULLETS}
|
||||||
|
```
|
||||||
|
|
||||||
|
**Tone options:**
|
||||||
|
- confidently professional (default)
|
||||||
|
- technically precise
|
||||||
|
- executive-level strategic
|
||||||
|
- enthusiastically genuine (entry-level)
|
||||||
|
|
||||||
|
### Resume Condensing (2 pages → 1 page)
|
||||||
|
```
|
||||||
|
This resume is 2 pages but needs to be 1 page. Condense it by: (1) Combining or cutting the weakest bullet points, (2) Tightening language (removing filler words), (3) Prioritizing recent and relevant experience, (4) Suggesting what to cut entirely. Target role: {TITLE}. Keep the strongest achievements and the content most relevant to this specific role.
|
||||||
|
{PASTE_RESUME}
|
||||||
|
```
|
||||||
|
|
||||||
|
### LinkedIn-to-Resume Conversion
|
||||||
|
```
|
||||||
|
Convert this LinkedIn profile text into a polished resume format. Restructure for resume conventions: (1) Convert narrative paragraphs into bullet points, (2) Add quantification where possible, (3) Prioritize achievements over responsibilities, (4) Remove first-person pronouns, (5) Target this toward a {SPECIFIC_ROLE}.
|
||||||
|
{PASTE_LINKEDIN_CONTENT}
|
||||||
|
```
|
||||||
|
|
||||||
|
## Output Format
|
||||||
|
|
||||||
|
Produce the resume in markdown matching this structure:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# {FULL_NAME}
|
||||||
|
|
||||||
|
{PROFESSIONAL_SUMMARY}
|
||||||
|
|
||||||
|
- **Email:** {EMAIL}
|
||||||
|
- **Website:** [{WEBSITE}]({URL})
|
||||||
|
- **GitHub:** [{GITHUB}]({URL})
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Work Experience
|
||||||
|
|
||||||
|
### {TITLE} | [{COMPANY}]({URL}) — *{DATES}*
|
||||||
|
|
||||||
|
- {BULLET_1}
|
||||||
|
- {BULLET_2}
|
||||||
|
- {BULLET_3}
|
||||||
|
- {BULLET_4}
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Skills & Technology
|
||||||
|
|
||||||
|
- {SKILL_CATEGORY_1}: {COMMA_SEPARATED_SKILLS}
|
||||||
|
- {SKILL_CATEGORY_2}: {COMMA_SEPARATED_SKILLS}
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Education
|
||||||
|
|
||||||
|
- {DEGREE}, {INSTITUTION}
|
||||||
|
|
||||||
|
*References available upon request.*
|
||||||
|
```
|
||||||
|
|
||||||
|
## The Perfect Resume Prompt Formula
|
||||||
|
|
||||||
|
For any prompt not covered by the templates above, follow this formula:
|
||||||
|
|
||||||
|
1. State role, seniority, and industry
|
||||||
|
2. Describe specific context (company size, team, market)
|
||||||
|
3. Include actual numbers and metrics
|
||||||
|
4. Specify the target role and company type
|
||||||
|
5. Define the output format (bullets, summary, skills list)
|
||||||
|
6. Set the tone (professional, technical, executive, energetic)
|
||||||
|
7. State what to avoid (generic phrases, overused verbs, specific cliches)
|
||||||
|
|
||||||
|
## Execution Rules
|
||||||
|
|
||||||
|
1. **Always read the user's existing resume first** before generating anything
|
||||||
|
2. **Never fabricate metrics** — use the user's real numbers or mark placeholders with `[X]`
|
||||||
|
3. **Iterate** — first outputs are rarely perfect. Offer to refine after generating
|
||||||
|
4. **Preserve the user's authentic voice** — AI should enhance, not replace
|
||||||
|
5. **When a JD URL is provided**, fetch it with webfetch before tailoring
|
||||||
|
6. **Apply ATS formatting rules** to every output
|
||||||
|
7. **Each bullet point must** start with an action verb, include a measurable result, and be 1-2 lines
|
||||||
|
8. **Avoid AI resume cliches**: "spearheaded", "leveraged", "utilized", "synergy", "dynamic", "passionate", "results-driven", "self-starter"
|
||||||
|
9. **After generating**, offer the improvement tools (critique, tone adjustment, condensing)
|
||||||
|
10. **Write the final output** to the user's resume file (e.g. `resume.md`) only when explicitly asked
|
||||||
Reference in New Issue
Block a user