Dependent Tool: This Skill requires the

agent-browser

CLI. For installation instructions, refer to the

compatibility

field in the frontmatter. Command Reference: references/agent-browser.md

• Use browser only for login, all other operations via API: The browser is only used to establish session cookies; search/filter/evaluation are all done via API, which is over 100 times faster
• All fetch requests must be called within the main session (104-sourcing): Independent sessions of Subagents cannot share login cookies
• eval only supports ES5 syntax: Use

  var

  instead of

  const/let

  , do not use arrow functions, otherwise eval will throw errors

1. Job Title: What position are you searching for? (e.g., Telemarketing, Sales, Engineer)
2. Work Location: What work locations can candidates accept? (e.g., Taipei City, Banqiao District, New Taipei City)
3. Hard Requirements: What are the necessary conditions? (e.g., work experience, education background, specific skills or certifications)
4. Employment Status: Do you only want to view job seekers in specific employment statuses? (Default: No restriction)
   • No restriction:

     empStatus=0

   • Employed (seeking job change):

     empStatus=1

   • Unemployed (available immediately):

     empStatus=2

1. Ideal Candidate Profile: What traits or backgrounds are most valued for this position? What past experiences are particularly preferred?
2. Red Flags: What situations need to be excluded? (e.g., frequent job changes, specific industry backgrounds, long employment gaps)
3. Bonus Items: Other nice-to-have conditions? (e.g., experience with specific software, language proficiency)

• Search Keywords: Used for the

  kws

  parameter in the API
• Hard Filter Criteria: Basis for JS filtering logic
• Qualitative Evaluation Standards: Basis for scoring after viewing candidate profiles

1. Directly open the Recruitment Management Platform (with existing session to check if already logged in)
   bash

   agent-browser --session-name 104-sourcing open https://vip.104.com.tw/rms/index

2. Get current status
   bash

   agent-browser --session-name 104-sourcing snapshot -i

   Interpret the snapshot output to determine the current page status:
3. If already on vip.104.com.tw (Recruitment Management Platform) → directly proceed to Stage 3, no need to log in
4. If redirected to login page → request account and password from the user, note two scenarios:
   • Full Login (snapshot shows both email and password input fields): Enter account and password
   • Password Re-verification (snapshot shows only password input field, no email field): 104 sometimes only requires re-entering the password when the session expires, no need to re-enter the email
   bash

   agent-browser --session-name 104-sourcing fill @eX "{user-provided email}"  # Only for full login
   agent-browser --session-name 104-sourcing fill @eX "{user-provided password}"
   agent-browser --session-name 104-sourcing click @eX   # Login button
   agent-browser --session-name 104-sourcing snapshot -i

5. If MFA appears (snapshot shows OTP input field)
   • Request 6-digit email verification code from the user

   • agent-browser --session-name 104-sourcing fill @eX "verification code"

   • agent-browser --session-name 104-sourcing press Enter

6. Confirm access to vip.104.com.tw
   • If duplicate login dialog appears: Find "Log out current account" in snapshot → click
   • If ad popup appears (promotional text like "Enhance Exposure" in screenshot): Find close button in snapshot → click

agent-browser --session-name 104-sourcing eval "
fetch('https://auth.vip.104.com.tw/api/search/searchResult?contactPrivacy=0&kws=%E9%9B%BB%E9%8A%B7%E4%BA%BA%E6%89%8D&city=6001001000&workExpTimeType=all&sex=2&empStatus={0|1|2}&updateDateType=1&sortType=RANK&readStatus=all&plastActionDateType=1&page=1&ec=105', {credentials:'include'})
  .then(function(r){return r.json()})
  .then(function(d){
    window._fixedDate = d.result.fixedUpdateDate;
    window._totalPages = d.result.pageInfo.total_page;
    window._allCandidates = d.result.data;
    window._p1done = true;
  });
'fetching page 1...'
"

sleep 3 && agent-browser --session-name 104-sourcing eval "JSON.stringify({done:window._p1done, fixedDate:window._fixedDate, totalPages:window._totalPages, count:window._allCandidates&&window._allCandidates.length})"

Important:

fixedUpdateDate

must be obtained from the response of Page 1, and this value must be included in all subsequent page requests to ensure result consistency.

Important: Each API call can successfully save a maximum of 50 entries; entries exceeding this limit will fail silently (listed in

params.fail

). You must send requests in batches of 50 entries, and use synchronous XHR to get real-time results (async fetch + window variables will be lost after page navigation).

undefined

"Currently, N candidates have been filtered based on search list data. Would you like to perform in-depth resume analysis? (This will additionally read self-introduction, desired salary, and industry experience; it takes longer but provides more accurate evaluation)"

• eval only supports ES5: Do not use

  const/let

  , arrow functions, or template literals, otherwise SyntaxError will be thrown
• API fetch requests must be called within the main session (104-sourcing): Independent sessions of Subagents do not have login cookies

• expJobNote

  contains HTML tags; use

  .replace(/<[^>]+>/g, '')

  to clean it before analysis

• fixedUpdateDate

  must be obtained from the response of Page 1 and used for all subsequent page requests
• If the session expires (fetch returns "Not logged in"), re-execute the login process in Stage 2
• Do not add "人才" (talent) to search keywords: The 104 search mechanism is not precise enough; adding "人才" will easily result in HR positions like "Talent Specialist" or "Talent Consultant", which interfere with results. Use only the job title instead (e.g., Telemarketing, Sales, Engineer)
• Must use isDuplicate=0 for saveResume:

  -1

  is account-level duplicate check (candidates saved in any folder are considered duplicates), which will cause a large number of candidates to be skipped silently;

  0

  will force save to the target folder
• Max 50 entries per batch: The actual maximum number of successfully saved entries per saveResume request is 50; entries exceeding this limit will be listed in

  params.fail

  without error prompts, so be sure to batch in units of 50
• Use synchronous XHR instead of async fetch for saveResume: Async fetch requires additional sleep + reading window variables, which will be lost once page navigation occurs; synchronous XHR returns results directly and is more reliable
• Page navigation will clear all window variables: As long as

  open

  is executed to switch pages,

  window._qualified

  ,

  window._allCandidates

  , etc. will all be lost, and you need to re-fetch and filter