skills/cv-creator/SKILL.md
Professional CV and resume builder transforming career narratives into ATS-optimized, multi-format resumes. Integrates with career-biographer for data and competitive-cartographer for positioning. Generates PDF, DOCX, LaTeX, JSON Resume, HTML, and Markdown. Activate on 'resume', 'CV', 'ATS optimization', 'job application'. NOT for cover letters, portfolio websites (use web-design-expert), LinkedIn optimization, or interview preparation.
npx skillsauth add curiositech/windags-skills cv-creatorInstall 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.
Professional resume builder that transforms structured career data into ATS-optimized, professionally formatted resumes.
Works with: career-biographer, competitive-cartographer, web-design-expert, typography-expert
GitHub: github.com/erichowens/cv-creator
npm install && npm run exampleBuilt through multi-skill orchestration (8 skills, 9 phases).
User: "Create a resume for senior software engineer roles"
CV Creator:
1. Request CareerProfile (from biographer or direct input)
2. Request PositioningStrategy (from cartographer or skip)
3. Request target role/company (optional)
4. Generate resume with clean formatting
5. Calculate ATS score and provide recommendations
6. Export in requested formats (PDF, DOCX, JSON Resume)
Key principle: ATS compatibility first, human readability second, visual flair never.
| Format | Use Case | |--------|----------| | PDF | Email applications, job boards, print | | DOCX | Recruiter submissions, editable | | JSON Resume | Developer portfolios, programmatic | | HTML | Portfolio websites, responsive | | Markdown | Version control, git-based management | | LaTeX | Academic CVs (optional) |
| Template | Best For | |----------|----------| | Modern Minimalist | Tech roles (Engineers, Data Scientists) | | Professional Traditional | Finance, Legal, Senior Executives | | Creative Hybrid | Design Engineers, UX Researchers | | Academic CV | PhD, Professors, Researchers |
| Category | Points | Criteria | |----------|--------|----------| | Formatting | 30 | Single-column, standard fonts, no graphics | | Structure | 20 | Summary, Skills, Experience, Education present | | Content | 30 | Proper lengths, skills count, metrics in bullets | | Keywords | 20 | Job description coverage (or 15 for general) |
Target: 85+ out of 100
Use for:
Do NOT use for:
What it looks like: Colorful infographics, skill bars, profile photo, two-column layout Why wrong: ATS systems can't parse graphics or complex layouts Instead: Use Minimalist template with clean, single-column text format
What it looks like: "Seeking a challenging role in a growth-oriented company..." Why wrong: Wastes space, provides no information Instead: Professional summary with specific metrics and target role
What it looks like: 40+ skills including outdated technologies Why wrong: Dilutes expertise, unclear proficiency Instead: List 15-20 most relevant skills for target role
What it looks like: "Managed a team", "Worked on backend systems" Why wrong: Doesn't show impact or value Instead: "Led team of 5 to deliver microservices migration, reducing deployment time by 70%"
What it looks like: Mixed date formats, different bullet styles, varying fonts Why wrong: Looks unprofessional, confuses ATS parsers Instead: Strict consistency throughout
| Issue | Cause | Fix | |-------|-------|-----| | ATS Score <70 | Complex formatting, graphics | Switch to Minimalist, remove images | | Keyword Coverage <60% | Not tailoring to job description | Extract keywords, add to Core Skills | | Exceeds 2 pages | Too verbose, old roles included | Consolidate old roles, limit bullets | | Generic summary | No positioning insights | Include specific metric, state target role | | Long bullets | Trying to explain entire project | Split into multiple bullets, focus on outcome |
| Experience | Pages | |------------|-------| | Entry-level (0-3 years) | 1 page | | Mid-level (3-10 years) | 1-2 pages | | Senior-level (10+ years) | 2 pages max |
Never exceed 2 pages, even for very senior roles.
references/resume-protocol.md - Complete 8-step generation protocol, ATS scoring, before/after examplesreferences/formatting-rules.md - Best practices, templates, output formats, success metricsreferences/interfaces-integration.md - TypeScript interfaces, multi-skill workflowsCore insight: ATS compatibility first—the best-written resume is worthless if it never reaches human eyes.
Use with: career-biographer (content) | competitive-cartographer (positioning) | web-design-expert (portfolio)
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.