Liepin Job Search Assistant

Problem

In job-search workflows, candidates often have to repeat resume synchronization, job search, and application confirmation. Hand-writing HTTP calls can easily miss authentication details, parameter shapes, or state recovery, and makes it harder to audit an automated flow. This skill focuses on common Liepin operations through a local liepin-cli command surface, assuming the CLI is already available.

How It Works

The skill prefers calling liepin-cli instead of constructing ad hoc requests. The main path includes:

• Identity state: inspect or recover token state, and guide the user through authorization setup when needed.
• Resume handling: fetch a summary with resume get, confirm missing fields, then update only what is relevant.
• Job search: use job search to retrieve structured results that can be filtered by preference.
• Application confirmation: show the job details and wait for explicit confirmation before submitting with job apply.

When machine-readable output is useful, request --output json so downstream filtering, comparison, and logging remain stable.

Boundaries

This skill is only for Liepin-related tasks and should not be used for unrelated business operations. Before applying, the user must see the specific job details. --job-kind should reuse the type code returned by search results rather than guessing. If the token is expired or a local sample payload is missing, resolve the prerequisite state first instead of assuming the file exists.