skills/job-application-optimizer/SKILL.md
Strategic job application planning and Resume SEO optimization. Approaches applications like marketing campaigns with market research, opportunity qualification, and content optimization. Activate on 'optimize resume', 'tailor resume', 'ATS optimization', 'job fit score', 'should I apply'. NOT for initial career narratives (career-biographer), portfolio design (cv-creator), or market positioning (competitive-cartographer).
npx skillsauth add curiositech/windags-skills job-application-optimizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Strategic job application planning and "Resume SEO" optimization. This skill teaches Claude to approach job applications like a marketing campaign - researching the market, qualifying opportunities, and optimizing content for maximum conversion.
Activate on:
NOT for:
Treat job applications like search engine optimization:
| SEO Concept | Resume Equivalent | |-------------|-------------------| | Search query | Job description | | Web page | Resume | | Keywords | Skills & requirements | | Meta description | Professional summary | | H1 heading | Job title/headline | | Content quality | Achievement metrics | | Keyword density | Skills frequency (2-4% optimal) | | Backlinks | Referrals & endorsements | | Page speed | Scan time (<6 seconds) |
Before optimizing, determine if the job is worth applying to:
APPLY signals:
SKIP signals:
Like SEO keyword research, extract and prioritize:
Primary Keywords (must include):
Secondary Keywords (should include):
Long-tail Keywords (nice to have):
LIGHT Tailoring (match >80%)
MEDIUM Tailoring (match 60-80%)
AGGRESSIVE Tailoring (match 50-65%)
Before submitting, verify:
Format:
Structure:
Content:
Keywords:
For job search campaigns:
Daily:
Weekly:
Monthly:
This skill works with:
cv-creator-mcp:
analyze_job → score_match → suggest_tailoring → score_ats
career-biographer: Provides the structured CareerProfile that cv-creator-mcp uses.
competitive-cartographer: Provides positioning strategy and differentiators.
## Job: Senior Backend Engineer at TechCorp
### Step 1: Analyze Job
- Required: Go, Kubernetes, PostgreSQL, 5+ years
- Preferred: Kafka, gRPC, AWS
- Signals: Remote-friendly ✓, Equity ✓
### Step 2: Score Match
- Overall: 78/100 (GOOD_MATCH)
- Matched: Go, Kubernetes, PostgreSQL, Kafka, gRPC
- Missing: None critical
- Gap: 0 years (8 > 5 required)
### Step 3: Recommendation
- Apply: YES
- Tailoring Level: LIGHT
- Estimated Time: 15 minutes
### Step 4: Tailoring Actions
1. Reorder skills: Go first, then K8s, PostgreSQL
2. Add to summary: "Specialized in event-driven microservices"
3. Ensure "Senior Backend Engineer" exact match in headline
### Step 5: ATS Check
- Score: 85/100 ✓
- Quick wins: Add AWS certification date
### Step 6: Apply
- Resume: alex-chen-techcorp-v1.pdf
- Cover letter: Generated with connection hook
- Tracking: Added to spreadsheet
| Metric | Target | Alex Chen Example | |--------|--------|-------------------| | Applications/week | 20-30 | 25 | | Response rate | >10% | 16% | | Interview rate | >5% | 8% | | Offer rate | >2% | 4% | | ATS pass rate | >80% | 92% | | Avg match score | >70% | 78% |
When optimizing, produce:
Match Analysis Report
Tailored Resume
Cover Letter
Application Tracker Entry
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.