ResumeSkills is a collection of AI-agent skills for improving resumes, preparing job applications, practicing interviews, and planning career moves. It is intended for job seekers, career changers, and professionals using Claude Code for tasks such as ATS checks, job-description matching, resume tailoring, and salary negotiation. The catalogue entry consists of the project's career-focused skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Paramchoudhary/ResumeSkills --skill resume-version-managergit clone --depth 1 https://github.com/Paramchoudhary/ResumeSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/paramchoudhary/resumeskills/resume-version-manager)<a href="https://agentmods.dev/skills/paramchoudhary/resumeskills/resume-version-manager"><img src="https://agentmods.dev/badge/skills/paramchoudhary/resumeskills/resume-version-manager.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 332 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.01986 |
| Opus 5 | $0.00008 | $0.00993 |
| Sonnet 5 | $0.00003 | $0.00397 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
resume-version-manager scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- resume-version-manager — 100% identical, 0 lines differ
- resume-version-manager — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Version Manager
When to Use This Skill
Use this skill when the user:
- Has multiple resume versions to manage
- Needs to track tailored resumes
- Wants to maintain a master resume
- Is applying to many different roles
- Mentions: "resume versions", "master resume", "different versions", "track resumes", "which resume"
Core Capabilities
- Create and maintain master resume document
- Track tailored resume versions
- Organize resume versions by role/industry
- Maintain consistent source of truth
- Streamline resume updates
- Prevent version confusion
The Version Management Problem
Common Pain Points:
- "Which version did I send to Company X?"
- "Where's my most recent resume?"
- "I have 15 resume files and don't know which is best"
- "I forgot to update my resume after that project"
- "I keep tailoring from different base versions"
The Solution: A systematic approach with:
- One master resume (source of truth)
- Organized tailored versions
- Clear naming conventions
- Update workflow
Master Resume Concept
What is a Master Resume?
A comprehensive document containing:
- ALL your experiences (not just recent)
- ALL bullet points you've ever written
- Every achievement, project, skill
- Full details (even if they won't fit on one page)
Purpose: Source of truth to pull from when tailoring
Master Resume Structure
# MASTER RESUME - [YOUR NAME]
Last Updated: [Date]
## CONTACT INFORMATION
[Full contact details]
## PROFESSIONAL SUMMARY VERSIONS
[Summary for Role Type A]
[Summary for Role Type B]
[Summary for Role Type C]
## ALL SKILLS
### Technical Skills
[Complete list by category]
### Soft Skills
[Complete list]
### Industry Knowledge
[All domains]
## PROFESSIONAL EXPERIENCE
### Company Name | Title | Dates
**All Bullets (choose best for each application):**
• Bullet 1 (leadership focused)
• Bullet 2 (technical focused)
• Bullet 3 (results focused)
• Bullet 4 (collaboration focused)
• Bullet 5 (additional achievement)
• Bullet 6 (additional achievement)
**Keywords this experience covers:**
[List of keywords this job demonstrates]
### Previous Company | Title | Dates
[Same format...]
## EDUCATION
[Complete education history]
## CERTIFICATIONS
[All certifications ever earned]
## PROJECTS
[All notable projects]
## VOLUNTEER / ADDITIONAL
[All other relevant experience]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 352 lines · 16 tokens per session scan A ddf1acc97694
resume-version-manager is a skill published in the GitHub repository Paramchoudhary/ResumeSkills (2,169 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,986 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.