사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/gaket/talent-agent --skill tailor-resume시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
tailor-resume
Inputs
- Target JD (and
score-fitoutput if available). profile/cv.mdandprofile/facts.json(source of truth).
Steps
- Extract the JD's top 6–8 keywords (languages, frameworks, ML/data tools, responsibilities).
- Select content: education first for students; then the 2–3 most relevant experiences/projects by keyword overlap. Drop weak items to stay on one page.
- Rewrite bullets: action verb + what + tool + result. Reuse metrics only if present in facts.json. Mirror JD wording only where the fact supports it (e.g. "REST API" if FastAPI service exists).
- Reorder the skills line to put JD-matching, evidenced skills first. Never add a skill not in
facts.json.skillsor a project stack. - Verify: produce a mapping table — each bullet → source fact id (
exp1,proj1…). Any bullet without a source is removed or flagged as[NEEDS FACT]and you ask the user. - Output to
output/resume-<company>-<role>.md(default) or.tex(simple one-column LaTeX, no exotic packages). Keep to one page: ≤ ~550 words, ≤ 4 bullets per entry. - Show a short diff summary: what moved up, what was cut, keywords covered / still missing (missing ones go back to
score-fitgaps, not into the resume).
Rules
- No invented experience, employers, dates, metrics, or skills. Rephrasing is fine; fabrication is not.
- Keep contact info and education dates exactly as in facts.json.
- ATS-friendly: no tables/columns/images in the resume itself; standard headings.

