give-me-job
AGENTS.md6 starsChanged 5 months agoMITView on GitHub
Use this repository as a Korea-only job-application package generator, not as an automatic application submitter. When the user asks to run the full workflow, says "give me job", or wants a complete company-specific application package for the Korean hiring market: The sections above describe using this repository to produce an application package. This section describes changing the repository itself. 1. Explore. Read the affected files and their callers before editing. Docs in this repository have drifted from the code before,…
- Reads credentials
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- application-packagerSkill
- 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 AGENTS.md into the rules it gives an agent
21 rules. About 0 are common, 8 are distinctive, and 13 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Use this repository as a Korea-only job-application package generator, not as an automatic application submitter.
- Distinctive: line 7
When the user asks to run the full workflow, says "give me job", or wants a complete company-specific application package for the Korean …
- Very specific: line 10
Use the application workflow skills under skills/ as the domain workflow steps.
- Very specific: line 11
Create or update one package under applications/<company-role>/.
- Very specific: line 12
Keep all strong cover-letter claims grounded in resume.md.
- Distinctive: line 13
Stop when evidence is missing, HR review finds a blocker, or the next action would submit, send, log in, bypass CAPTCHA, or transmit …
- Distinctive: line 14
Treat non-Korean hiring workflows as out of scope unless the user explicitly asks to adapt the repository later.
- Very specific: line 18
Use skills/resume-intake/SKILL.md when resume.md is missing or weak.
- Very specific: line 19
Use skills/jd-analyzer/SKILL.md for JD or hiring-post analysis.
- Very specific: line 20
Use skills/company-values-analyzer/SKILL.md only when company values, culture, mission, or talent-profile material is provided.
- Very specific: line 21
Use skills/cover-letter-writer/SKILL.md for Korean cover-letter drafts and evidence maps.
- Very specific: line 22
Use skills/hr-reviewer/SKILL.md before any final text is prepared.
- Very specific: line 23
Use skills/interview-prep/SKILL.md after draft/final text exists to prepare evidence-grounded interview defense.
- Very specific: line 24
Use skills/application-packager/SKILL.md to assemble the final package and manual submission checklist.
- Distinctive: line 33
Explore: Read the affected files and their callers before editing.
- Distinctive: line 41
Verify: Run the checks below and fix failures before committing.
- Distinctive: line 44
When a guideline in any document conflicts with the repository's real state, trust the terminal output and fix the document.
- Very specific: line 59
Run npm run test:install whenever you touch tools/install-*.mjs, tools/skill-registry.mjs, tools/give-me-job-cli.mjs, or the files list in …
- Very specific: line 77
No API key, access token, or other issued credential.
- Distinctive: line 89
Before publishing or pushing release changes, run:
- Very specific: line 105
Do not commit generated user application packages under applications/.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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
give-me-job Repository Instructions
Use this repository as a Korea-only job-application package generator, not as an automatic application submitter.
Default Workflow
When the user asks to run the full workflow, says "give me job", or wants a complete company-specific application package for the Korean hiring market:
- Read
agent.mdfirst. - Use the application workflow skills under
skills/as the domain workflow steps. - Create or update one package under
applications/<company-role>/. - Keep all strong cover-letter claims grounded in
resume.md. - Stop when evidence is missing, HR review finds a blocker, or the next action would submit, send, log in, bypass CAPTCHA, or transmit personal information.
- Treat non-Korean hiring workflows as out of scope unless the user explicitly asks to adapt the repository later.
Skill Routing
- Use
skills/resume-intake/SKILL.mdwhenresume.mdis missing or weak. - Use
skills/jd-analyzer/SKILL.mdfor JD or hiring-post analysis. - Use
skills/company-values-analyzer/SKILL.mdonly when company values, culture, mission, or talent-profile material is provided. - Use
skills/cover-letter-writer/SKILL.mdfor Korean cover-letter drafts and evidence maps. - Use
skills/hr-reviewer/SKILL.mdbefore any final text is prepared. - Use
skills/interview-prep/SKILL.mdafter draft/final text exists to prepare evidence-grounded interview defense. - Use
skills/application-packager/SKILL.mdto assemble the final package and manual submission checklist.
Working On This Repository
The sections above describe using this repository to produce an application package. This section describes changing the repository itself.
Development Loop
- Explore. Read the affected files and their callers before editing. Docs in this repository have drifted from the code before, so confirm that a script or path a document mentions actually exists.
- Plan. Identify every file the change touches, including validators and packaging lists. Keep each commit atomic.
- Edit. Make the smallest diff that does the job. Do not reformat untouched lines, delete comments you were not asked to remove, or rename things opportunistically.
- Verify. Run the checks below and fix failures before committing. If a check fails, read the actual error before changing the approach.
When a guideline in any document conflicts with the repository's real state, trust the terminal output and fix the document.
Commands
This repository has no lint step and no build step. Do not invent one.
npm test # full suite; the default gate for any change
npm run test:skills # skill contracts, packaging lists, and release files only
npm run test:jobs # schedule and ranking fixtures only
npm run test:install # installer: install, upgrade, conflict, force, uninstall
npm run test:release # npm test + test:install; what publishing runsRun npm run test:install whenever you touch tools/install-*.mjs,
tools/skill-registry.mjs, tools/give-me-job-cli.mjs, or the files list in
package.json. npm test alone does not cover the installer.
Repository-Specific Constraints
These are enforced by validators and will fail the suite:
SKILL.mdfrontmatter accepts onlynameanddescription. Any other field is rejected. Install-time additions such asallowed-toolsare injected bytools/install-adapters.mjs, not written into the source file.- A skill's
descriptionmust be at least 120 characters. - Validation scripts must not live in
tools/. Public checks go insupport/validate/, release-only checks intests/validate/. - A new workflow tool's flag allowlist in
tools/install-adapters.mjsmust match the generated OpenCode tool policy exactly. - Adding a file to the support bundle means updating
supportFilesintools/install-layout.mjsandfilesinpackage.jsontogether. - No API key, access token, or other issued credential.
.env.exampleandtools/env.mjsare blocked from returning.
Do Not Edit
applications/,data/, and.tmp-*directories. These are generated and git-ignored..github/workflows/publish.ymlrelease triggers without saying so. Pushing av*.*.*tag publishes to npm, and a published version cannot be reused.
Release Discipline
Before publishing or pushing release changes, run:
npm testEquivalent manual checks:
node tests/validate/validate-skills.mjs
node tools/init-application.mjs --company demo --role backend --out .tmp-release-check --force
node support/validate/validate-application.mjs .tmp-release-check/demo-backend
node support/validate/validate-job-schedule.mjs
node support/validate/validate-job-ranking.mjsDo not commit generated user application packages under applications/.
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.

