kyoungbinkim/give-me-job / skills/resume-intake
resume-intake
VerifiedBuild or improve a job seeker's resume.md source file from conversational career input. Use when the user wants to create resume.md, organize new-grad or experienced career history, convert raw experiences into STAR/CAR evidence, add missing metrics, or prepare reusable career evidence for cover letters and job applications. 한국어 요청도 포함합니다 - 이력서 작성, 이력서 정리, 경력기술서, 경력 정리, 커리어 정리, 자소서 소재 정리, 내 경험 정리해줘, 신입 이력서, 경력직 이력서.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.6 KB |
| examples/experienced-resume.md | markdown | 2.0 KB |
| examples/new-grad-resume.md | markdown | 1.4 KB |
| references/resume-schema.md | markdown | 5.0 KB |
references/resume-schema.md
View on GitHub# Resume Schema
Canonical structure for `resume.md`. All give-me-job skills read this file
as the source of truth.
## Top-Level Structure
```txt
resume.md
├── Personal Info
├── Target Role
├── Summary
├── Work Experience (experienced: required / new-grad: if any)
├── Projects (always required)
├── Education
├── Skills
└── Certificates & Awards (optional)
```
## Metadata
Add this block at the top after each intake session:
```md
<!--
last-updated: YYYY-MM-DD
career-type: new-grad | experienced
target-role: value
intake-version: n
-->
```
Increment `intake-version` when updating an existing `resume.md`. Use `1` for
the first structured intake.
## Personal Info
```md
## Personal Info
- Name: [Full Name]
- Email: [email]
- Phone: [+82-10-xxxx-xxxx or local format]
- LinkedIn: [url]
- GitHub / Portfolio: [url]
- Location: [City, Country]
```
Rules:
- Phone should be international format when applying abroad.
- At least one profile link is required. If missing, ask for it or mark the
missing field clearly instead of inventing one.
## Target Role
```md
## Target Role
[Role title] at [Company type or specific company]
```
Write `Unknown` when the target is not decided.
## Summary
```md
## Summary
[2-3 sentences. Written last, after all evidence units are complete.]
```
Do not write this section until all work and project evidence units are at
`Medium` strength or above. If any key evidence remains `Low`, leave a short
placeholder such as `Pending stronger evidence.` and ask follow-up questions.
## Work Experience
Experienced candidates require this section. New graduates may omit it when
they have no work, internship, or part-time experience relevant to the target
role.
```md
## Work Experience
### [Job Title] - [Company Name], [City]
*[Month Year] - [Month Year or Present]*
**Team / Org:** [Optional: team name or department]
**Headcount managed:** [Optional: number if applicable]
- [STAR/CAR bullet 1]
- [STAR/CAR bullet 2]
<!-- strength: High -->
```
Rules:
- List roles in reverse chronological order.
- Each bullet is one STAR/CAR unit: action verb, what was done, method or
scale, and measurable or observable result.
- Use 2-5 bullets per role.
- The strength comment is mandatory and must be `High`, `Medium`, or `Low`.
STAR/CAR bullet format:
```txt
[Action verb] [what you did] [at what scale or with what method],
resulting in [measurable or observable outcome].
```
## Projects
Projects are always required. Include school projects, side projects,
open-source contributions, or portfolio work.
```md
## Projects
### [Project Name]
*[Month Year] - [Month Year] | [Your Role] | [Tech Stack]*
[Optional: link to repo or demo]
- [STAR/CAR bullet]
- [STAR/CAR bullet]
<!-- strength: Medium -->
```
Rules:
- State the candidate's specific role, such as `sole developer`,
`backend lead`, or `contributor`.
- Do not list a project if there is no concrete action and observable result.
- The strength comment is mandatory and must be `High`, `Medium`, or `Low`.
## Education
```md
## Education
### [Degree Name] - [School Name]
*[Graduation Year or Expected Year]*
- GPA: [X.X / 4.0] (include only if >= 3.5/4.0 or equivalent)
- Thesis / Capstone: [Title, one sentence description]
- Relevant coursework: [Only if directly relevant to target role]
- Honors / Awards: [Dean's list, scholarship, etc.]
```
## Skills
```md
## Skills
- **Programming languages:** [e.g., Python, TypeScript, Java]
- **Frameworks & tools:** [e.g., React, FastAPI, Docker, PostgreSQL]
- **Human languages:** [e.g., Korean (native), English (business)]
```
Rules:
- List only skills the candidate can discuss in an interview.
- Do not rate proficiency with stars, bars, or vague levels.
## Certificates & Awards
```md
## Certificates & Awards
- [Certificate Name], [Issuing Body], [Year]
- [Award Name], [Context / Scope], [Year]
```
Optional. Include only directly relevant or nationally/internationally
recognized items.
## Evidence Strength
Every work and project entry must end with one comment:
```md
<!-- strength: High -->
<!-- strength: Medium -->
<!-- strength: Low -->
```
- `High`: concrete role, action, method or scale, result, and metric are
present.
- `Medium`: concrete action and observable result are present, but metric or
scope is weak.
- `Low`: mostly attitude, intent, responsibility, or generic description. Ask
follow-up questions before using it as a core cover-letter claim.
## Evidence References
Assign stable `EXP-001` IDs to evidence units. Preserve existing IDs across
reordering and edits, and record the original section and entry title plus the
current line or bullet location, for example:
```txt
EXP-001: Projects > Reservation API Consistency Project > bullet 1
EXP-002: Work Experience > Backend Engineer - FixturePay > bullet 2
```
An older resume without IDs remains readable. Add identifiers before ready
validation without changing its facts. Do not create an `Experience Bank`
section or treat generated application language as new source evidence.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |