菜单
This skill should be used when the user asks to "投递简历", "申请岗位", "发送在线简历", "先聊再投", "apply to a job", "submit a resume", or "send an online resume".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/LIghtJUNction/BossKit --skill resume-application命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | resume-application |
| description | This skill should be used when the user asks to "投递简历", "申请岗位", "发送在线简历", "先聊再投", "apply to a job", "submit a resume", or "send an online resume". |
| version | 0.1.0 |
Run a controlled, pure-command-line BossKit workflow for one AI Agent opportunity. Treat conversation as qualification, not as permission to submit a resume. Keep every platform write explicit, narrow, and verifiable.
Check local authentication state with:
boss status --platform zhipin
Inspect the sanitized online resume snapshot with:
boss account resume show
Find and inspect candidates with:
boss search "AI Agent" --platform zhipin
boss ls --platform zhipin
boss show <LOCAL_JOB_ID>
Choose exactly one best role at a company. Record the company, title, local cached job ID, salary evidence, schedule evidence, and relevant skill fit.
Stop before contact when the stated monthly salary floor is below 10K, the role is not an AI Agent role, or a duplicate same-company conversation or application already exists.
Treat missing or ambiguous salary and double-weekend information as unresolved hard gates, never as implied acceptance.
Begin with the platform greeting only after the target has passed initial inspection:
boss chat greet <LOCAL_JOB_ID> --yes
Never submit a resume on first contact. Never attach a resume to the greeting.
Personalize the opening to the exact role and one relevant strength. Avoid batch-identical introductions, generic spam, and any pitch for an automation product or workflow.
Read the exact conversation before composing another message:
boss chat history <LOCAL_JOB_ID> --limit 20
boss chat inbox <LOCAL_JOB_ID>
Send at most one concrete question per message:
boss chat send --message "<ONE_CONCRETE_QUESTION>" <LOCAL_JOB_ID> --yes
Wait for a response before asking the next question or expanding activity. Never scale to more roles while the selected company conversation remains unresolved.
Learn the following naturally across the conversation:
Ask about the equipment policy neutrally. Never demand or directly ask for a MacBook Pro.
Stop after rejection. Send no unsolicited follow-up. Ask once for a rejection reason only when explicitly requested.
Require all conditions before considering submission:
Confirm an AI Agent role and one-company/one-role uniqueness.
Confirm salary evidence at or above 10K.
Confirm explicit double-weekend evidence.
Collect sufficient conversational evidence for welfare and working-context assessment, while allowing unanswered non-hard preferences to remain noted.
Confirm no rejection and no prior submission to the exact target.
Refresh the sanitized resume preview with boss account resume show.
Inspect current capability with:
boss account resume --help
Current BossKit exposes only boss account resume show; it has no platform
resume-submission command. When no documented boss account resume submit or
equivalent appears in current help, STOP and report the missing capability.
Never fabricate the command, call a raw endpoint, or claim that submission
occurred.
If a supported submission command appears in a future version, first present the exact company, title, local cached job ID, sanitized resume preview, and collected gate evidence. Request explicit confirmation immediately before that single submission. Never auto-submit or reuse earlier consent. Execute only the documented command, then verify the platform write through a documented post-write read command. Report failure or unverifiable state honestly.
Return a compact record without secrets, remote IDs, or PII:
resume_submitted: true | false
exact_target: <company> / <title> / <local cached job ID>
resume_preview: <sanitized snapshot identity and section counts>
user_confirmation: <immediate confirmation present | absent>
conversation_evidence: <safe summary of greeting, replies, and hard-gate answers>
salary_gate: pass | fail | unknown
double_weekend_gate: pass | fail | unknown
rejection_status: not_rejected | rejected | unknown
no_duplicate_proof: <same-company role and prior-submission checks>
submission_verification: verified | failed | unsupported
Set resume_submitted: true only after a supported platform write and
independent post-write verification both succeed. Otherwise keep it false and
state the exact blocker.