resume-intake

resume-intake is a skill for Claude Code from kyoungbinkim/give-me-job. It costs 125 tokens per session (1,462 once invoked), scanned A, original, MIT.

A guided process for turning a job seeker's career details into a structured resume.md file. It can organize experiences and turn them into evidence-based examples without adding facts that were not provided.

In plain words
What is it for?
Creating or updating resume.md, organizing new-graduate or experienced-worker history, and preparing examples for cover letters and job applications.
Why use it?
Raw career history can be incomplete or difficult to reuse when writing applications. This process helps keep the resume organized and grounded in the person's actual experience.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the give-me-job plugin — 8 skills shipped together

Good fit Creating or updating resume.md, organizing new-graduate or experienced-worker history, and preparing examples for cover letters and job applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kyoungbinkim/give-me-job/resume-intake
Install

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.

Any agent
npx skills add kyoungbinkim/give-me-job --skill resume-intake
Clone the repo
git clone --depth 1 https://github.com/kyoungbinkim/give-me-job

Made for: Claude Code.

Or install give-me-job, the plugin that ships this one along with the rest of its 8 skills.

Wrote 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.

agentmods badge for resume-intake

README.md
[![agentmods](https://agentmods.dev/badge/skills/kyoungbinkim/give-me-job/resume-intake/github.svg)](https://agentmods.dev/skills/kyoungbinkim/give-me-job/resume-intake)
Your own site
<a href="https://agentmods.dev/skills/kyoungbinkim/give-me-job/resume-intake"><img src="https://agentmods.dev/badge/skills/kyoungbinkim/give-me-job/resume-intake/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for resume-intake

Your own site · 80×15
<a href="https://agentmods.dev/skills/kyoungbinkim/give-me-job/resume-intake"><img src="https://agentmods.dev/badge/skills/kyoungbinkim/give-me-job/resume-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,462 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00125 $0.01462
Opus 5 $0.00063 $0.00731
Sonnet 5 $0.00025 $0.00292
Haiku 4.5 $0.00013 $0.00146

Measured 3d ago against content hash c117877fbdd8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

resume-intake 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 3d 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.

skills/resume-intake/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resume Intake

Use this skill to turn raw career material into a structured resume.md that other give-me-job skills can trust.

Trigger

Use this skill when resume.md is missing, thin, outdated, or lacks evidence that can support a Korean cover letter.

Do Not Trigger

Do not use this skill when the user already has a usable resume.md and only needs JD analysis, cover letter drafting, HR review, or packaging.

Autonomy Level

DoF: LOW

Follow user-provided facts only. Do not infer missing employers, dates, metrics, awards, tools, responsibilities, or outcomes.

Permitted inferences:

  • Career type from stated graduation date, work history, or years of experience.
  • Evidence strength from specificity, role clarity, and observable result.

Prohibited inferences:

  • Do not upgrade a school project into professional work.
  • Do not turn participation into ownership unless the user says they owned the work.

Input Contract

Required context:

  • Raw career material from the user or an existing resume.md.

Optional context:

  • Target role, target company, JD, or desired cover-letter questions.

Required parameters:

  • target_role: target role when available, otherwise unknown.
  • career_type: new-grad, experienced, or unknown.

Outputs produced:

  • resume.md draft, a patch/update plan, or focused follow-up questions.

Workflow

  1. Read references/resume-schema.md before creating or rewriting resume.md.
  2. Determine whether the user is new-grad, experienced, or still unknown.
  3. Read an existing resume.md if present. Preserve valid facts, but migrate old Profile, Core Summary, Experience Bank, or Work History structures into the canonical sections.
  4. Create or update the metadata block:
    • last-updated: today's date
    • career-type: new-grad or experienced
    • target-role: target role or Unknown
    • intake-version: increment the existing value, or use 1
  5. Collect raw experiences in the user's language first. Do not force every field before making progress, but ask for missing facts that materially affect evidence quality.
  6. Build the canonical top-level sections in this order:
    • Personal Info
    • Target Role
    • Summary
    • Work Experience for experienced candidates, or for new graduates only when they have relevant work/internship/part-time experience
    • Projects
    • Education
    • Skills
    • Certificates & Awards only when relevant
  7. Split work and project material into STAR/CAR bullets:
    • action verb
    • what was done
    • method, scale, or constraints
    • measurable or observable result

Read the full file on GitHub · 163 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 3d ago Changed · +10 lines c117877fbdd8
  2. 12d ago First seen · 153 lines · 125 tokens per session scan A f079004f7cf4

Subscribe to this mod's changes

resume-intake is a skill published in the GitHub repository kyoungbinkim/give-me-job (5 stars, last pushed 3d ago), licensed MIT. It adds 125 tokens to every session and 1,462 once invoked, about $0.0006 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-31.