offer

/offer: Autumn recruitment progress management

Organize scattered recruitment emails, screenshots, and chat records into a reviewable job search funnel, recording company, position, date, status, next step, and notes. Do not write application numbers, passwords, verification codes, or irrelevant personal information into public resources.

Resource location

ASu resources support two layouts, located in the following order: the Claude Code installation layout uses ../../assets/asu/ and ../../references/asu/; the repository plugin layout uses ../../assets/ and ../../references/. Each candidate is a pair of assets/references directories: use that directory pair only when the assets directory contains both application-tracker.html and application-tracker-overview.svg, and the corresponding references directory contains email-monitoring.md , to avoid mistakenly using the resources of other skills.application-tracker.html is the editable job search progress table,application-tracker-overview.svg is the preview image.

If the skill is copied separately to another directory, first locate assets/asu/、references/asu/ and the repository plugin's assets/、references/successively upward from the current skill directory; do not recreate existing resources.

Workflow

1. Extract the date, company, position, current status, next step, and necessary notes from the emails, recruitment websites, or screenshots provided by the user.
2. Merge duplicate records for the same company and same position; later assessment, interview, rejection, or offer statuses override the earlier "Applied".
3. Update status only when there is evidence; ordinary automatic receipts cannot be inferred as an interview or offer, and insufficient evidence should be marked as "To be confirmed".
4. When the user does not specify a file location, copy application-tracker.html to the desktop, and return the absolute path of the generated file.
5. When the user requests to check the mailbox or perform a daily check, use the browser to handle it; login, passwords, MFA, verification codes, and CAPTCHA are completed by the user and are not saved on their behalf.
6. When the user needs to also create a resume file, switch to /make-resume; when the user needs to enhance experience, switch to /great-resume。

Status specification

Default statuses include: Applied, Screening, Assessment in progress, Interview, Offer, Rejected/Closed, To be confirmed. For each update, try to state the source of evidence and the next action, to facilitate later review.

Default delivery

By default, provide the progress table file, a summary of identified records, status changes, a next-step checklist, and missing information. Do not write the user's real job search records into the skill's template or README.