Resume auto-apply
Use this skill only for an application task with a user-provided resume or an explicit request to collect one. Treat every application as an externally visible action and keep a reviewable record.
Operating contract
- Ask for the resume file (PDF/DOCX/structured text), target roles/locations, work authorization, salary or seniority constraints, contact details, and which sites/tools may be used. If a required field is missing, list it and pause before submission.
- Parse facts into a local profile and one or more resume versions. Preserve source wording and mark any inferred or generated wording; never invent employment, education, dates, metrics, credentials, or legal status. Offer edits as a draft and require user approval before saving a canonical version.
- Before browser work, show the target jobs, domains, account/session assumptions, selected resume version, fields to be filled, and scope (one job or batch). Use only browser/agent/MCP tools available in the current environment; read the relevant browser and site-strategy references first.
- Classify each target as a known recruiting platform, company ATS/careers site, direct email, or unknown. Select a strategy from the site reference. Unknown or blocked sites stop for human handling.
- Navigate and fill only after the user has authorized the listed scope. Keep passwords, OTPs, CAPTCHA solving, and security questions user-controlled. Never bypass anti-automation, paywalls, access controls, or site terms.
- Run a dry-fill when possible. Map fields to profile facts, flag ambiguous or sensitive answers, and request correction. Keep free-text answers concise, truthful, and role-specific.
- At the final submit/send step, pause for an explicit confirmation that identifies the exact job(s), destination(s), resume version, and message/attachments. For a batch, require a per-batch confirmation and stop on any material change.
- After submission or a reported failure, append an idempotent application record and show a concise audit summary. Do not claim success without an on-page confirmation or a sent-mail result.
- Keep local data minimal, encrypted where available, and redact PII from console output. Support export and deletion on request. Read
references/privacy-security.md for retention and consent details.
Routing references
- Data model and local record format: references/data-schema.md.
- Domain classification and field strategies: references/site-strategies.md.
- Browser/agent capability detection and fallbacks: references/browser-tools.md.
- Privacy, consent, and stopping rules: references/privacy-security.md.
- Isolated validation checklist: references/acceptance.md.
- Market and open-source research notes: references/job-source-research.md.
- Deterministic helpers:
scripts/classify_url.py and scripts/log_application.py.
Completion criteria
A run is complete only when (a) required profile fields are present or explicitly marked unavailable, (b) every target has a chosen strategy, (c) the user-approved submission scope is unchanged, and (d) each attempted target has a success, failure, or needs-user-action record with evidence and no secrets in logs.
1---2name: resume-auto-apply3description: Collect, complete, tailor, and track job applications from a user-provided resume and job links, using authorized browser or agent tools. Use for requests to auto-fill or submit applications; do not use for resume-only editing or generic job advice.4---56# Resume auto-apply78Use this skill only for an application task with a user-provided resume or an explicit request to collect one. Treat every application as an externally visible action and keep a reviewable record.910## Operating contract1112- Ask for the resume file (PDF/DOCX/structured text), target roles/locations, work authorization, salary or seniority constraints, contact details, and which sites/tools may be used. If a required field is missing, list it and pause before submission.13- Parse facts into a local profile and one or more resume versions. Preserve source wording and mark any inferred or generated wording; never invent employment, education, dates, metrics, credentials, or legal status. Offer edits as a draft and require user approval before saving a canonical version.14- Before browser work, show the target jobs, domains, account/session assumptions, selected resume version, fields to be filled, and scope (one job or batch). Use only browser/agent/MCP tools available in the current environment; read the relevant browser and site-strategy references first.15- Classify each target as a known recruiting platform, company ATS/careers site, direct email, or unknown. Select a strategy from the site reference. Unknown or blocked sites stop for human handling.16- Navigate and fill only after the user has authorized the listed scope. Keep passwords, OTPs, CAPTCHA solving, and security questions user-controlled. Never bypass anti-automation, paywalls, access controls, or site terms.17- Run a dry-fill when possible. Map fields to profile facts, flag ambiguous or sensitive answers, and request correction. Keep free-text answers concise, truthful, and role-specific.18- At the final submit/send step, pause for an explicit confirmation that identifies the exact job(s), destination(s), resume version, and message/attachments. For a batch, require a per-batch confirmation and stop on any material change.19- After submission or a reported failure, append an idempotent application record and show a concise audit summary. Do not claim success without an on-page confirmation or a sent-mail result.20- Keep local data minimal, encrypted where available, and redact PII from console output. Support export and deletion on request. Read `references/privacy-security.md` for retention and consent details.2122## Routing references2324- Data model and local record format: [references/data-schema.md](references/data-schema.md).25- Domain classification and field strategies: [references/site-strategies.md](references/site-strategies.md).26- Browser/agent capability detection and fallbacks: [references/browser-tools.md](references/browser-tools.md).27- Privacy, consent, and stopping rules: [references/privacy-security.md](references/privacy-security.md).28- Isolated validation checklist: [references/acceptance.md](references/acceptance.md).29- Market and open-source research notes: [references/job-source-research.md](references/job-source-research.md).30- Deterministic helpers: `scripts/classify_url.py` and `scripts/log_application.py`.3132## Completion criteria3334A run is complete only when (a) required profile fields are present or explicitly marked unavailable, (b) every target has a chosen strategy, (c) the user-approved submission scope is unchanged, and (d) each attempted target has a success, failure, or needs-user-action record with evidence and no secrets in logs.
diyiwuyan