Skills liepin-cli

📦

liepin-cli

Name: liepin-cli
Author: xllin

v0.3.0 Content revision r1 High Risk 🌐 Network access📁 Filesystem access🔑 Env variables⚙️ External commands

Manage Liepin Jobs from the CLI

Liepin job workflows can be hard to run from chat because search, resume, and application steps use separate commands. This skill guides Claude, Codex, and Claude Code through the local CLI with structured outputs and confirmation steps.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "liepin-cli" from https://skillstore.io/skills/xllinbupt-liepin-cli.md and its manifest at https://skillstore.io/api/skills/xllinbupt-liepin-cli/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/xllinbupt-liepin-cli.md Signed manifest GET /api/skills/xllinbupt-liepin-cli/manifest Signed lockfile GET /api/skills/xllinbupt-liepin-cli/lockfile

Test it

Using "liepin-cli". Search for AI product manager jobs in Shanghai.

Expected outcome:

A ranked list of matching roles with company, location, salary range, experience needs, and reasons each role may fit.

Using "liepin-cli". Check whether my resume is ready for these roles.

Expected outcome:

A concise resume readiness summary with missing fields, weak sections, and suggested updates before applying.

Using "liepin-cli". Apply to this selected job after I confirm.

Expected outcome:

A confirmation request that shows the job title, company, job kind, and account impact before any application is submitted.

Security Audit

High Risk

v5 • 7/8/2026 Open versioned report

The audit confirms real risks from authenticated network calls, environment-token access, plaintext local token configuration, and hidden credential-file use. Many high-looking static hits are false positives from Markdown backticks, parameter names, and entropy in readable multilingual text. No prompt injection text was found in the cited files.

Files scanned

508

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:57-63 liepin_mcp.py:193-198 liepin_mcp.py:209-218

Authenticated Resume and Job Application Side Effects

The skill can fetch resume data, update resume modules, and submit job applications through authenticated MCP calls. SKILL.md requires confirmation before applying, but the Python CLI exposes direct apply and update commands without enforcing chat-level confirmation.

The workflow explicitly includes resume review and job application, and the implementation directly calls user-apply-job and resume-toolkit. This is intended functionality, but it has real external account effects.

Medium

liepin_mcp.py:70-75 liepin_mcp.py:125-128 liepin_mcp.py:147-149 liepin_mcp.py:266

Configurable Endpoint Receives User Token

The MCP URL can be read from configuration or setup arguments, and the client sends the user token in an HTTP header. A malicious or mistaken endpoint override could receive the token and job or resume payloads.

The code sets x-user-token on each request and allows the URL to come from configuration or the setup --url argument. The risk depends on endpoint control, so confidence is high but not absolute.

Capability review items (11)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

reference.md:62

Hidden file in home directory

- Token 优先级:`--token` > `LIEPIN_USER_TOKEN` > 本地配置文件(`~/.config/liepin-cli/config.json`)

The reference documents token use from a hidden config file in the user home directory. Hidden credential files are sensitive and need clear storage protections.

Medium

liepin_mcp.py:75

Python HTTP libraries

req = urllib.request.Request(self.url, data=data, headers=headers, method="POST")

The code builds POST requests to the configured MCP URL with JSON payloads and authentication headers. This can transmit user resume and job data externally.

Medium

liepin_mcp.py:77

Python HTTP libraries

with urllib.request.urlopen(req, timeout=timeout) as resp:

The code performs outbound urlopen calls to the configured MCP endpoint. The requests use the user token and can carry sensitive job or resume data.

Medium

liepin_mcp.py:40

Python file write/append

with open(CONFIG_PATH, "w", encoding="utf-8") as f:

The setup flow writes configuration to a local file that can include the user token. Plaintext token storage in user config is a real credential exposure risk.

Medium

liepin_mcp.py:125

Configuration library

url = config.get("mcp_url", DEFAULT_MCP_URL)

The MCP URL is read from local configuration before the token is used. If the config is changed, authenticated requests could be redirected to another endpoint.

Medium

reference.md:62

Hidden file access

- Token 优先级:`--token` > `LIEPIN_USER_TOKEN` > 本地配置文件(`~/.config/liepin-cli/config.json`)

The documented token priority includes a hidden local config file. This confirms filesystem-based credential access for the CLI workflow.

Low

liepin_mcp.py:18

Python HTTP libraries

import urllib.request

The Python file imports urllib for outbound HTTP requests. This is intended, but it confirms network capability inside the skill tooling.

Low

liepin_mcp.py:24

Hardcoded URL

DEFAULT_MCP_URL = "https://open-agent.liepin.com/mcp/user"

The hardcoded URL is the default external Liepin MCP service endpoint. It is expected functionality, but it fixes an external network destination for authenticated requests.

Low

liepin_mcp.py:46

Python environment access

user_token = config.get("user_token") or os.environ.get("LIEPIN_USER_TOKEN", "")

The code reads LIEPIN_USER_TOKEN from the process environment. This is legitimate configuration, but it accesses a secret-bearing environment variable.

Low

liepin_mcp.py:46

Configuration library

user_token = config.get("user_token") or os.environ.get("LIEPIN_USER_TOKEN", "")

The same token lookup uses local config first and environment fallback. Both sources can contain a sensitive Liepin user token.

Low

SKILL.md:28

Hardcoded URL

若用户尚未安装 `liepin-cli`,引导其参考 [liepin-tech-2026/liepin-cil](https://github.com/liepin-tech-2026/liepin-

The skill directs users to an external GitHub repository for CLI installation. This is manual guidance, but it introduces supply-chain trust in code outside the skill package.

Risk Factors

🌐 Network access (9)

_meta.json:8 liepin_mcp.py:18 liepin_mcp.py:75 liepin_mcp.py:77 liepin_mcp.py:24 liepin_mcp.py:139 SKILL.md:10 SKILL.md:11 SKILL.md:28

📁 Filesystem access (3)

liepin_mcp.py:40 reference.md:62 reference.md:62

🔑 Env variables (3)

liepin_mcp.py:46 liepin_mcp.py:46 liepin_mcp.py:125

⚙️ External commands (23)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/xllinbupt-liepin-cli/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/xllinbupt-liepin-cli/security.svg)](https://skillstore.io/skills/xllinbupt-liepin-cli?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/xllinbupt-liepin-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/xllinbupt-liepin-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/xllinbupt-liepin-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

xllin. (2026). liepin-cli security audit report (audit version 5) [Author version 0.3.0]. Skillstore. https://skillstore.io/skills/xllinbupt-liepin-cli/audits/5

BibTeX citation

@techreport{xllin-xllinbupt-liepin-cli-2026,
  author = {xllin},
  title = {liepin-cli security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/xllinbupt-liepin-cli/audits/5},
  note = {Author version 0.3.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "liepin-cli security audit report (audit version 5)"
version: "0.3.0"
type: report
authors:
  - name: "xllin"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/xllinbupt-liepin-cli/audits/5"
identifiers:
  - type: other
    value: "skillstore:xllinbupt-liepin-cli:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

100

Spec Compliance

What You Can Build

Search Matched Roles

Find Liepin roles by title, city, salary, experience, education, and company filters, then compare the strongest matches.

Review Resume Readiness

Fetch the current Liepin resume, summarize missing sections, and prepare changes before applying to selected roles.

Run Structured Job Workflows

Use machine-readable CLI output to parse search results, preserve job kind values, and prepare confirmed application steps.

Try These Prompts

Set Up Authentication

Help me check whether Liepin CLI is installed and guide me through authentication without exposing my token.

Search for Jobs

Search Liepin for product manager roles in Shanghai, then summarize the most relevant results in a table.

Review Resume Fit

Fetch my Liepin resume, compare it with the search results, and list gaps I should fix before applying.

Apply with Confirmation

Search for senior AI product roles, verify job kind from each result, show the target role details, and ask before applying.

Best Practices

Confirm the target job details before every application.
Use machine-readable output when comparing multiple jobs or parsing resume fields.
Keep tokens private and use Liepin auth flows instead of pasting secrets into chat.