BOSS Zhipin Job Matching Assistant

Problem

The hard part of job matching is often not collecting listings, but connecting JD requirements, candidate profile fields, and search context into reviewable recommendations. This skill aligns your profile, BOSS Zhipin job data, and JD evidence instead of returning an opaque score.

How it works

• Profile parsing: extracts target roles, skills, experience, city, salary floor, work arrangement, and deal-breakers from text, PDF, or attachments; missing items are marked as “not provided”.
• Job capture: uses the bundled boss-zhipin-scraper subskill to read logged-in listings through Chrome/CDP, fetches JD details when needed, limits default pages, and reuses existing JSON/CSV results.
• Matching and ranking: compares core skills/responsibilities, experience/industry, location, work arrangement, salary, and education preferences, then labels roles as strong match, fair match, or cautious match.
• Traceability: conclusions cite JD text or listing fields and distinguish confirmed matches, partial matches, gaps, and unknowns.

Boundaries

• Use it for personal job research and public job information only; do not bypass login, captchas, or rate limits.
• OCR from scanned PDFs, missing JDs, and abnormal salary fields reduce confidence; the skill does not invent skills, projects, education, or experience.
• If you have not declared a hard constraint, the skill records risk rather than silently rejecting roles.