AgentStack
SKILL verified MIT Self-run

Managing Resume Versions

skill-vibewith-brent-claude-resume-skills-resume-state · by vibewith-brent

Manages resume projects and versions. Use first when the user starts resume work to initialize projects, import files, create versions before changes, or switch between resume variants for different roles.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-vibewith-brent-claude-resume-skills-resume-state

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README — it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-vibewith-brent-claude-resume-skills-resume-state)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Managing Resume Versions? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Resume State Manager

Overview

Manage resume versions across multiple projects/target roles. Each version preserves the complete YAML and generated artifacts, enabling rollback, A/B comparison, and organized multi-role job search workflows.

Quick Start

Initialize a Project

uv run scripts/init_project.py ml_engineer

Import Existing Resume

uv run scripts/import_resume.py resume.pdf --project ml_engineer

Creates v1 with:

  • Copied source PDF in sources/
  • Extracted text in versions/v1/extracted_text.txt
  • Placeholder YAML in versions/v1/resume.yaml

Create New Version

uv run scripts/create_version.py --tag google --notes "Tailored for Google SWE"

Copies YAML from active version to new v2 (or v3, etc.).

List Versions

uv run scripts/list_versions.py

Output:

ml_engineer versions:

  v1     [import]  2025-11-30  Imported from resume.pdf
* v2     [derived] 2025-11-30  google - Tailored for Google SWE

Switch Active Version

uv run scripts/switch_version.py v1

Get Active YAML Path

uv run scripts/get_active.py
# .resume_versions/projects/ml_engineer/versions/v2_google/resume.yaml

Export for Submission

uv run scripts/export_version.py v2 ~/Desktop/applications/google/ --format pdf

Compare Versions

uv run scripts/diff_versions.py v1 v2

Storage Structure

.resume_versions/
├── config.json                    # Active project setting
└── projects/
    └── ml_engineer/
        ├── project.json           # Version history + metadata
        ├── sources/               # Original PDFs/DOCXs (immutable)
        ├── versions/
        │   ├── v1/
        │   │   ├── resume.yaml
        │   │   └── extracted_text.txt
        │   └── v2_google/
        │       ├── resume.yaml
        │       ├── resume.typ
        │       └── resume.pdf
        └── jobs/                  # Cached job postings

Store Location

Scripts find .resume_versions using this search order:

  1. Environment variable: RESUME_VERSIONS_PATH (if set)
  2. Upward search: From current directory upward to root
  3. Global fallback: ~/.resume_versions

This allows:

  • Running commands from any subdirectory of your project
  • Using a global store for all projects (~/.resume_versions)
  • Overriding location with export RESUME_VERSIONS_PATH=/custom/path

Workflow Integration

State scripts provide path resolution for other skills:

# Get active YAML and pipe to formatter
YAML=$(uv run scripts/get_active.py)
uv run ../resume-formatter/scripts/yaml_to_typst.py "$YAML" executive -o "${YAML%.yaml}.typ"
uv run ../resume-formatter/scripts/compile_typst.py "${YAML%.yaml}.typ"

Commands Reference

| Command | Description | |---------|-------------| | init_project.py | Create new project | | import_resume.py | Import PDF/DOCX as new version | | create_version.py | Branch new version from active | | list_versions.py | Show version history | | switch_version.py | Change active version | | get_active.py | Print active YAML path | | export_version.py | Copy files to target | | diff_versions.py | Compare YAML changes |

Common Options

  • --project, -p: Specify project (default: active project)
  • --tag, -t: Version tag suffix (e.g., google, shortened)
  • --notes, -n: Description of changes

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.