resume-extractor
Extract and categorize yearly career data into structured components (what_i_did, my_thoughts, performance). Use when processing raw yearly markdown files into organized sections.
Best use case
resume-extractor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Extract and categorize yearly career data into structured components (what_i_did, my_thoughts, performance). Use when processing raw yearly markdown files into organized sections.
Teams using resume-extractor should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/resume-extractor/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How resume-extractor Compares
| Feature / Agent | resume-extractor | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Extract and categorize yearly career data into structured components (what_i_did, my_thoughts, performance). Use when processing raw yearly markdown files into organized sections.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Resume Extractor Skill ## Purpose Transform raw yearly career documents into **three structured markdown files** that separate facts from reflections from metrics. ## Task Given a year (e.g., 2024), process all related markdown files in that year's directory and extract: 1. **what_i_did_YYYY.md** - Factual accomplishments - Projects delivered - Technologies used - Systems built/maintained - Responsibilities held - Concrete deliverables 2. **my_thoughts_YYYY.md** - Personal growth & reflections - What I learned - Challenges faced and how I overcame them - Skills developed - Areas of growth - Key insights or "aha" moments 3. **performance_YYYY.md** - Quantifiable impact - KPIs and metrics - Business outcomes - Performance improvements (latency, throughput, revenue, etc.) - Team impact (people mentored, processes improved) - Recognition or achievements ## Instructions ### Step 1: Discover Source Files - Use Glob to find all markdown files in the year directory (e.g., `./2024/*.md`) - Read each file to understand the content structure - Note: Files may be quarterly reviews, project timelines, retrospectives, or summaries ### Step 2: Intelligent Extraction For each source file, use your LLM capabilities to: - **Understand context**: Is this a quarterly review? A project description? A retrospective? - **Categorize content**: Which sections belong to what_i_did vs my_thoughts vs performance? - **Handle ambiguity**: Some content may fit multiple categories - use your judgment - **Preserve specifics**: Keep dates, numbers, project names, technology names exact ### Step 3: Structure Output Each output file should be well-organized with: - Clear section headers (## Projects, ## Technologies, ## Learnings, etc.) - Chronological ordering (Q1 → Q4) - Consistent formatting - Deduplication (if same achievement mentioned multiple times) ### Step 4: Validation Before writing output files, verify: - No information loss (all important details captured) - No duplication across the three files - Dates and metrics are accurate - Proper markdown formatting ### Step 5: Write Output Write the three files to the same directory as the source files: - `YYYY/what_i_did_YYYY.md` - `YYYY/my_thoughts_YYYY.md` - `YYYY/performance_YYYY.md` ## Example Input/Output ### Input: `2024/1분기.md` ```markdown # 2024 Q1 회고 이번 분기에는 백엔드 시스템 마이그레이션을 주도했다. PostgreSQL에서 MongoDB로 전환하면서 쿼리 성능이 40% 개선되었다. 이 과정에서 NoSQL 데이터 모델링에 대해 깊이 배울 수 있었다. ``` ### Output: `2024/what_i_did_2024.md` ```markdown ## Q1 - Projects - Led backend system migration from PostgreSQL to MongoDB - Redesigned data models for NoSQL architecture ``` ### Output: `2024/performance_2024.md` ```markdown ## Q1 - Impact - Query performance improved by 40% after migration ``` ### Output: `2024/my_thoughts_2024.md` ```markdown ## Q1 - Learnings - Gained deep understanding of NoSQL data modeling principles - Learned trade-offs between relational and document databases ``` ## Error Handling If you encounter: - **Missing files**: Report which year directory has no content - **Ambiguous content**: Make best judgment and note uncertainty in comments - **Invalid formats**: Parse what you can, skip malformed sections - **Encoding issues**: Try UTF-8, then fallback to other encodings ## Success Criteria - All three output files created - Content properly categorized - No information lost from source files - Consistent formatting and structure
Related Skills
email-extractor
Expert in email content extraction and analysis. **Use whenever the user mentions .eml files, email messages, says "Extract email information", "Using the email information", or requests to extract, parse, analyze, or process email files.** Handles email thread parsing, attachment extraction, and converting emails to structured markdown format for AI processing. (project, gitignored)
article-extractor
Extract clean article content from URLs (blog posts, articles, tutorials) and save as readable text. Use when user wants to download, extract, or save an article/blog post from a URL without ads, navigation, or clutter.
gsd:workflow:resume-project
Workflow for resuming a paused project
resume-generator
Generates and compiles a single-page US Letter LaTeX resume using selected experiences.
agentuity-cli-cloud-queue-resume
Resume message delivery for a paused queue. Requires authentication. Use for Agentuity cloud platform operations
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
u09955-decision-journal-maintenance-for-accessibility-services
Operate the "Decision Journal Maintenance for accessibility services" capability in production for accessibility services workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
u0225-oversight-uncertainty-communicator
Operate the "Oversight Uncertainty Communicator" capability in production for Human Oversight and Operator UX workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
u01482-constraint-compilation-for-healthcare-operations
Operate the "Constraint Compilation for healthcare operations" capability in production for healthcare operations workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
tzurot-council-mcp
Best practices for using the Council MCP server in Tzurot v3 development - When to consult external AI, how to structure prompts, model selection, and multi-turn conversations. Use when planning major changes or needing a second opinion.
typespec-m365-copilot-typespec-create-agent
Generate a complete TypeSpec declarative agent with instructions, capabilities, and conversation starters for Microsoft 365 Copilot Use when: the task directly matches typespec create agent responsibilities within plugin typespec-m365-copilot. Do not use when: a more specific framework or task-focused skill is clearly a better match.
typespec-create-agent
Generate a complete TypeSpec declarative agent with instructions, capabilities, and conversation starters for Microsoft 365 Copilot