agentsclimarketplace
Sign in

Application packager

Skill kyoungbinkim/give-me-job/skills/application-packager

Create a company-specific job application package from a JD, resume.md, cover letter drafts, HR review, and optional company values input. Use when the user wants 지원 패키지, submission checklist, application folder structure, final answer snippets, email draft support, or safe pre-submission preparation without automatic final submission.From its SKILL.md

Install
npx -y skills add kyoungbinkim/give-me-job --skill application-packager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 616 tokens by cl100k_base, as published. Nobody here has run it

Application Packager

Create submission-ready materials, but do not submit applications automatically.

Trigger

Use this skill after the JD analysis, cover letter draft/final, evidence map, HR review, and optional interview prep are ready or when the user asks to assemble a final Korean application package.

Do Not Trigger

Do not use this skill to bypass HR review, submit an application, send email, log in, solve CAPTCHA, or transmit personal information.

Autonomy Level

DoF: LOW

Create and validate the package structure deterministically. Do not mark an application submitted unless the user explicitly confirms manual submission.

Permitted inferences:

  • ASCII package slug from company and role.
  • Missing package files from the canonical package structure.

Prohibited inferences:

  • Do not create unsupported cover letter claims.
  • Do not invent deadlines, required documents, or submission status.

Input Contract

Required context:

  • Company name and role name.
  • JD or applications/<company-role>/jd-analysis.md.
  • resume.md.
  • Cover letter draft or final.
  • applications/<company-role>/evidence-map.md.
  • applications/<company-role>/hr-review.md.

Optional context:

  • Company values analysis.
  • applications/<company-role>/interview-prep.md.
  • Deadline, file requirements, and length limits.

Required parameters:

  • company: target company name.
  • role: target role title.

Outputs produced:

  • applications/<company-role>/workflow.md
  • applications/<company-role>/submission-checklist.md

Inputs

  • company name
  • role name
  • JD or JD analysis
  • resume.md
  • cover letter draft or final
  • optional company values analysis
  • deadline, file requirements, and length limits if available

Workflow

  1. Normalize the application slug as company-role.
  2. Create or propose the package structure from references/package-structure.md.
  3. Save JD analysis, company values analysis, cover letter draft/final, evidence map, and checklist.
  4. Save interview preparation when available.
  5. Check company name, role name, file names, length limits, and required attachments.
  6. Prepare manual submission snippets or email draft text when requested.
  7. Record submission status only after the user confirms what happened.

Hard Rules

  • Do not click or trigger a final submit/send action.
  • Do not bypass CAPTCHA, login, payment, consent, or sensitive personal information prompts.
  • Do not create unsupported claims that are absent from resume.md.
  • Do not auto-create user data during skill installation. Create files only when the user asks during a task.

Output

## Application Package
- Company:
- Role:
- Deadline:
- Package Path:
- Included Files:
- Missing Inputs:
- Interview Prep:
- Submission Checklist:
- Manual Submission Notes:

Fallback

If final cover letter text is not ready, call for cover-letter-writer and hr-reviewer work before packaging.

What ships with it: 2 files

2.1 KB alongside SKILL.md

examples/

references/

Gives 0 of the 12 instructions most hr recruiting skills give in 616 tokens

Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07

  • Quantify achievements with specific metricsin 14 of 356, across 6 files
  • Keep the resume under two pagesin 14 of 356, across 6 files
  • Request the full job description if not providedin 12 of 356, across 4 files
  • Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
  • Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
  • Map candidate experience to job requirementsin 11 of 356, across 3 files
  • Ask if the user wants adjustmentsin 11 of 356, across 3 files
  • Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
  • Request candidate background details if not providedin 10 of 356, across 2 files
  • Format experience bullets as action verb plus resultin 10 of 356, across 2 files
  • Ask for missing inputs before startingin 10 of 356, across 9 files
  • Use exact job description terminologyin 9 of 356, across 1 file

Said here and by no other author read

  • Normalize the application slug as company-role
  • Create the package structure from package-structure reference
  • Save all available analysis and draft files
  • Check file names, length limits, and required attachments
  • Prepare submission snippets when requested
  • Call fallback skills before packaging final cover letter

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.