Professional resume builder that transforms structured career data into ATS-optimized, professionally formatted resumes.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncv-creatorExecute the skills CLI command in your project's root directory to begin installation:
Fetches cv-creator from erichowens/some_claude_skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cv-creator. Access via /cv-creator in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
84
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
84
stars
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 |
|---|---|
| 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)
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
erichowens/some_claude_skills
erichowens/some_claude_skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Useful defaults in cv-creator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
cv-creator reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for cv-creator matched our evaluation — installs cleanly and behaves as described in the markdown.
We added cv-creator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend cv-creator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in cv-creator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend cv-creator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
cv-creator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
cv-creator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: cv-creator is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 49