Update the application tracker. Record replies (rejection, screening, interview, offer), log an application the user made by hand, or sweep the inbox for replies. Use when the user runs /seekter-log, says a company replied or rejected them, or asks to check emails for responses.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
All changes go through scripts/seekter.py; never edit front matter or skipped.md by hand. move changes the status inside the file (files never change folder) and appends a log line; moving a skip to any other status turns its table row into a file, and moving a file to skipped turns it into a row.
| User says | Command |
|---|---|
| "X rejected me" | python3 scripts/seekter.py move <url-or-file> rejected --note "<date>, <one line from the mail>" |
| "X invited me to a call / screening / interview" | move … interviewing --note "<stage, date, who>" |
| "Got an offer from X" | move … offer --note "<amount, deadline>" |
| "I applied to X myself" | check <url> first, then add --status applied --source manual --notes "applied by hand" |
| A hand-off is submitted after the record exists, with free-text answers | move … applied --note "<date, how>" --answers "<the answers exactly as sent>" (appended to the record's Answers section) |
| "Forget X" / "Don't apply to X again" | move … skipped --note "<reason>" and add X to the blacklist in profile/profile.md §7 |
Find the file first when the user only gives a company name: python3 scripts/seekter.py list | grep -i <company>. If several rows match, ask which role.
Follow "Reply analysis" in reference/sources/inbox.md: open the user's webmail in Claude in Chrome, collect messages since the last sweep, read bodies, not subjects, and match with the rejection regex there (then read the matched sentence; boilerplate like "if you are not selected" is a false positive).
Read every folder the profile's §11 table lists, and re-read that table each sweep rather than trusting a remembered count: the list grows. It went from three folders to four on 25 Sept when Action Required was added for mail that asks the candidate to act.
For each reply:
add it with --source inbox.move it to rejected / interviewing / offer with a one-line note and the mail date.Action Required folder so it is not buried in the hundreds of confirmations in Job Application. Move it back to Job Application once the thing is done. Rejections and "we received your application" mails never go there.Postings with no reply after 30 days: move … closed --note "no response after 30 days" only when the user asks for a clean-up.
python3 scripts/seekter.py index, then report in two lines: what moved where, and anything that needs the user.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Ship the Seekter kit to git. Branch, commit and push the tracked, person-independent files (skills, references, scripts, templates) after a run has taught the kit something. Use when the user runs /seekter-git or asks to commit, push, or open a PR for the changes made to Seekter itself.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up Seekter for a new candidate. Interviews the user one question at a time and writes profile/profile.md, profile/settings.json and profile/documents/. Use when the user runs /seekter-init, says "set up seekter", or when profile/profile.md is missing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarise the job search from the markdown tracker - funnel, response rate, what's working, where applications come from, what's pending on the user. Use when the user runs /seekter-report or asks how the search is going, for weekly numbers, or what to change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a daily job search and auto-apply session for the candidate in profile/profile.md. Use when the user runs /seekter-run or asks to start applications, search for jobs, run today's scan, or apply to postings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.