xllinbupt/mcp2skill

Overview

This skill provides a Liepin job-search and application tool that lets users search jobs, view and edit their resume, and submit applications on the Liepin platform. It uses Liepin’s MCP server API and requires two authentication tokens from the user's Liepin account. The skill is designed for interactive workflows: check resume, search for matching roles, review details, and apply after explicit confirmation.

How this skill works

The skill calls Liepin MCP endpoints via a local script to perform search, resume retrieval/update, and application actions. Before any operation, it verifies that the two required tokens (gateway token and user token) are configured; without them no requests are allowed. Search results can be returned in human-readable format or raw JSON for programmatic use, and apply-job requires an explicit user confirmation step.

When to use it

• When you want to find relevant jobs on Liepin by title, location, salary, or company
• When you need to view or update your resume modules (basic, experience, expectations, self-assessment)
• When you want to apply to a specific job after reviewing details and matching degree
• When integrating Liepin search/results into automation or downstream tools using JSON output
• When you must check token validity or reconfigure credentials before performing actions

Best practices

• Obtain and store both tokens via the MCP server page before using any commands; tokens expire after 90 days
• Always run my-resume and confirm key resume fields are complete before applying
• Use --json when scripting or feeding results into another system; use human-readable output for interactive review
• Respect rate limits (60 calls/minute) and avoid bulk automated submissions
• Never paste full tokens into logs or public channels; treat tokens as secrets

Example use cases

• Interactive job hunt: check resume, search “AI product manager” in Shanghai, filter matches, and apply to top choices after confirmation
• Targeted company search: search by companyName (e.g., ByteDance) and export JSON for tracking
• Resume update flow: modify the experience module then re-run searches to see updated match quality
• Automated pipeline: call list-tools to discover new MCP endpoints and integrate fresh fields into a hiring dashboard
• Apply workflow: fetch jobId/jobKind from search result, show details to the user, then run apply-job only after explicit consent