메뉴
Research all existing work/ (READMEs, refs) and output findings for the Documentor to merge into the current job's README. Use after the job post is documented in Apply to a job flow. Trigger: "research work", "existing work", /research-work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Stage and commit at repo root and in nested work when work/.git exists; push only the nested work repo (Apply-Work), never the Apply root. Run only when user explicitly says "save", "commit", or /save. Never save otherwise. In Claude Code and Cursor, /skills lists all.
Align resume and cover letter to the job post (keywords, reverse chronology, action verbs, quantifiable results, experience cutoff). Before building, ask user for any more info (e.g. people at company). Output: resume-alignment.md, cover-letter.md, and connection-message.md for Documentor. Trigger: "resume alignment", "align resume", /resume-alignment.
Take research output and produce structured, enhanced markdown documentation with mermaid diagrams. Use when user says "write up", "document", or /document-findings. In Claude Code and Cursor, /skills lists all.
Gather from a job post (URL, paste, or file) and follow links up to 5 levels deep. Use when user says "learn about this", "look at this", or /learn. In Claude Code and Cursor, /skills lists all.
Find hiring/recruiting contacts from the job post and LinkedIn, document them with links and tastes, and draft a LinkedIn connection message. Use in Apply flow after job is documented. Trigger: "recruiting contacts", "hiring people", "connection message", or when user provides recruiter LinkedIn URLs.
After step 6 in Apply to a job, validate the README and resume against all rules. On failure, Strategist diagnoses fix and Documentor applies; repeat until pass. Trigger: "validate", "validation", /validate-application.
| name | research-work |
| description | Research all existing work/ (READMEs, refs) and output findings for the Documentor to merge into the current job's README. Use after the job post is documented in Apply to a job flow. Trigger: "research work", "existing work", /research-work. |
Read all content under work/ (past applications, refs, work history) and write structured findings to work/{company}/{job}/work-research.md. The Documentor then merges this into the project README.
work/{company}/{job}/ from work/config.md. Output goes here. If a folder for that company/job already exists and the user might mean a different role, offer the choice: update that one or create a new job folder (do not ask them to type). If they choose new, add the new company/job to config and use it.work/. Enumerate every folder and file under work/ (directory listing or equivalent). Scan all work/{company}/{job}/ and work/ref/work-history/ folders that contain README.md. Do not rely on a single path; use the full enumerated list.If there is no work to research (no READMEs under work/ other than the current project, or work/ is effectively empty): ask the user to provide files, links, or pasted data about their work history or past applications. Alternatively, offer plan mode. Do not write an empty work-research.md; wait for input or plan mode.
List every folder and file under work/ (e.g. via directory listing or glob). Do not rely on a single path or config alone. From that list:
work/{company}/{job}/ and work/ref/work-history/ folder that contains README.md.For each path from step 1, read README.md. Capture:
work/ref/work-history/README.md, key roles, dates, and highlights.Create work/{company}/{job}/work-research.md with structured markdown:
Use clear headings (H2). No placeholder or made-up rows. The Documentor will merge this into the README and remove work-research.md.
At the end, offer the user the option to provide any additional info relevant to the application. If they provide it, add it to work-research.md (e.g. a section "Additional info (user-provided)") so the Documentor merge will include it in the README.