SuperAPI AI Directory

boss-agent-cli

Office & productivity

View repository

Updated 10-15 20:10

About this skill

boss-agent-cli

A BOSS Zhipin local assistance CLI dedicated to AI Agents. The default low-risk mode only performs local assistance, read-only first, user-triggered, and does not automatically reach out, perform batch operations, or scrape platform data.

Install

Skills CLI

npx skills add can4hou6joeng4/boss-skill

CLI (the runtime dependency of this skill; run it first if not installed)

uv tool install boss-agent-cli
patchright install chromium  # only needed for browser-assisted login

First Minute

Run in this order; no need to read the full documentation first:

boss doctor
boss schema
boss status
boss login   # only if status reports AUTH_REQUIRED / AUTH_EXPIRED

Completion criteria:

  • boss doctor Returns ok=true, or provides an executable error.recovery_action。
  • boss schema Returns a self-description of the current command, parameters, platform, and error codes—it is the source of truth for capabilities; do not hardcode the command table.
  • boss status Returns the current login state; when not logged in, the user actively executes boss login(QR code/browser interaction, which the Agent cannot do on the user's behalf).

Safe Candidate Loop

On the job seeker side, only this low-risk closed loop is recommended by default:

boss schema
boss search "Golang" --city 广州 --welfare "双休,五险一金"
boss detail <security_id>
boss shortlist add <security_id> <job_id>

Rules:

  • Call first boss schema, do not hardcode the complete command table.
  • Only parse the JSON envelope on stdout; treat stderr only as logs and progress information.
  • ok=false When error.code read error.recovery_action, do not guess the recovery steps.
  • --welfare is the core filtering capability, suitable for low-risk job searches and local organization.
  • Actions such as applying, greeting, communicating, and exchanging contact information should be done manually by the user back on the platform's official website.

Recruiter Boundary

On the recruiter side, only the low-risk job management entry point is retained by default:

boss schema
boss hr jobs list
boss hr jobs online <job_id>
boss hr jobs offline <job_id>

Candidate search, application submissions, online resumes, attached resumes, chat records, message replies, contact information exchange, and other chains involving personal information or platform relationship writes; the default low-risk mode will return COMPLIANCE_BLOCKED. When encountering such results, stop automation and return to the official page for the user to handle manually.

Output Contract

All commands follow the same stdout JSON envelope:

{
  "ok": true,
  "schema_version": "1.0",
  "command": "search",
  "data": [],
  "pagination": null,
  "error": null,
  "hints": {}
}
  • stdout: outputs only the JSON envelope.
  • stderr: outputs only logs and progress, controlled by --log-level .
  • exit code 0: ok=true。
  • exit code 1: ok=false, must read error.code、error.recoverable、error.recovery_action。

Recovery

Prioritize recovery according to the error envelope:

Error code Agent action
AUTH_REQUIRED / AUTH_EXPIRED / TOKEN_REFRESH_FAILED Have the user actively execute boss login, then run boss status
BROWSER_KERNEL_MISSING Run patchright install chromium then have the user log in again
RATE_LIMITED / NETWORK_ERROR Wait and then follow recovery_action retry
INVALID_PARAM Correct the parameters and retry, for example city, page number, benefit keywords
AI_NOT_CONFIGURED / AI_API_ERROR / AI_PARSE_ERROR Follow recovery_action configure or retry the AI capability
ACCOUNT_RISK / COMPLIANCE_BLOCKED Stop automation, use the platform's official website or official page to complete manually

Do not treat login downgrade, browser channels, or CDP as a means to circumvent risk controls.

References (local, installed with the skill)

  • references/usage-patterns.md: stable usage patterns—URL reuse of web filters, benefit keywords, local organization and export, AI-assisted chains, multi-platform notes, request rhythm.

Everything the Agent needs is sourced locally: for capabilities and parameters check boss schema, for environment diagnostics run boss doctor, for recovery actions read the error envelope's recovery_action。

Further reading (external, for human maintainers only, the Agent need not depend on it)

License

MIT