waltonwang-debug/boss-hiring-assistant-skill

A GitHub Skill for Chinese users, designed to help local lobsters complete tasks in Boss Zhipin recruitment scenarios:

• Resume screening
• Boss: Communicate within the platform
• Feishu bot arranged an appointment

This warehouse currently focuses on mainline skill solutions, not standalone programs or general-purpose RPA platforms.

Pre-use instructions

First, let’s clarify a practical boundary:

**Skill: This form does not strongly control agents (such as lobsters). **

This is not a problem unique to this project, but is determined by the skill form itself:

• Skill is more like a “rule package / operation manual / constraint instructions”
• It can significantly reduce the agent’s free play
• But unlike fixed actuators, it cannot force every action to be performed 100% as intended

So when trying this skill, it is recommended:

1. Start with some of the work For example, just run boss-screening first; don’t start filtering, communicating, and scheduling meetings right away.

2. Start with short runs For example, first have lobsters run for a short period, deal with a small group of candidates, and then gradually expand the scope.

3. First observe the real implementation results, then gradually relax Especially on a risk-controlled platform like Boss, you need to avoid the consequences caused by agents acting freely:

• Misreading pages
• Repeated reach
• Abnormal browser behavior
• Trigger boss risk control or forced login exit

If this is your first time trying, it is strongly recommended to verify it in the most conservative way:

• Only filter
• Small batches
• Short duration
• Review the report results first, then decide whether to continue communication and appointments

What can be done?

Currently, Skill is split into three types of independent services:

1. boss-screening Used to read online job postings and JDs, screen candidates, and summarize progress.

2. boss-chat Used for in-site boss communication, such as requesting resume attachments, confirming intentions, and collecting interview times.

3. boss-scheduling Used for Feishu bot meetings after candidate confirmation times.

By default, it is recommended to start with boss-screening.

Key Rules That Have Become Established in the Current Main Storyline

Besides the three types of services, the current main line has already solidified several important execution boundaries:

1. Reuse the logged-in Boss tab first Do not open a new Boss page by default to avoid losing the recruiter’s login status.

2. If the policy file is missing, read the JD first If there are no company-policy.yaml / approval-policy.yaml], the online JD is read first, then the default filter criteria are automatically generated, rather than having the user dictate rules from scratch.

3. Screening Service Prioritizes Unread/Unprocessed Candidates Instead of repeatedly reviewing all visible candidates, prioritize current incremental targets with real business value.

4. Candidate identity verification before sending messages from the boss site Avoid sending messages intended for candidate A to candidate B.

5. After requesting attachments for resumes, we will continue to follow up on closed loops