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
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.