application-packager
Skill6 starsChanged 5 months agoMITView on GitHub
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.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- company-values-analyzerSkill
- cover-letter-writerSkill
- hr-reviewerSkill
- interview-prepSkill
- jd-analyzerSkill
- job-searcherSkill
- resume-intakeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 11 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create submission-ready materials, but do not submit applications automatically.
- Distinctive: line 12
Use this skill after the JD analysis, cover letter draft/final, evidence map, HR review, and optional interview prep are ready or when the …
- Distinctive: line 16
Do not use this skill to bypass HR review, submit an application, send email, log in, solve CAPTCHA, or transmit personal information.
- Distinctive: line 22
Create and validate the package structure deterministically.
- Distinctive: line 31
Do not create unsupported cover letter claims.
- Distinctive: line 32
Do not invent deadlines, required documents, or submission status.
- Very specific: line 74
Create or propose the package structure from references/package-structure.md.
- Distinctive: line 77
Check company name, role name, file names, length limits, and required attachments.
- Distinctive: line 80
Run structure validation for newly initialized templates.
- Very specific: line 85
Use state.json as the machine-readable preparation state and generate the workflow.md status summary from it.
- Distinctive: line 99
Do not click or trigger a final submit/send action.
- Distinctive: line 100
Do not bypass CAPTCHA, login, payment, consent, or sensitive personal information prompts.
- Very specific: line 101
Do not create unsupported claims that are absent from resume.md.
- Distinctive: line 102
Do not auto-create user data during skill installation.
- Very specific: line 121
If final cover letter text is not ready, call for cover-letter-writer and hr-reviewer work before packaging.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdapplications/<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
- Normalize the application slug as
company-role. - Create or propose the package structure from
references/package-structure.md. - Save JD analysis, company values analysis, cover letter draft/final, evidence map, and checklist.
- Save interview preparation when available.
- Check company name, role name, file names, length limits, and required attachments.
- Prepare manual submission snippets or email draft text when requested.
- Record submission status only after the user confirms what happened.
- Run structure validation for newly initialized templates. Run ready validation
for completed answers, checking required questions, length rules, evidence
references, completed current final review, and unresolved blockers. Only
successful ready validation records
ready-for-user-review.
Use state.json as the machine-readable preparation state and generate the
workflow.md status summary from it. Keep recruitment progress in the tracker.
Record interruption reasons and next actions; reuse completed steps only while
their reviewed input hashes remain current. Legacy packages without current
review metadata require revalidation and remain readable without overwriting
their existing prose. User risk acceptance never waives unresolved blockers.
An AI request from CLI, TUI, or dashboard is a prepared prompt, not a completed package. Execute it in the existing agent, save the requested files, validate, and reload the interface. Installation, upgrade, and uninstall must not touch resume facts, saved jobs, tracking data, or application packages.
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

