Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

UP 简历 - 让 Agent 帮你写简历找工作

v1.0.1

UP 简历 AI 求职助手。创建专业简历、搜索校招/社招/实习岗位、JD 对照优化、简历诊断、每日求职监控、智能投递指导。当用户说"创建简历"、"编辑简历"、"搜索校招"、"找工作"、"优化简历"、"投递"、"监控校招"时使用。

0· 243·1 current·1 all-time
by叁拾@hellosanshi·duplicate of @hellosanshi/clawjob-test
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
The skill's name, description, and detailed instructions align with a resume/job-search/auto-apply assistant and consistently call MCP tools (resume.*, campus.*) that match the stated purpose. However, the manifest declares no required credentials/binaries while the runtime SKILL.md repeatedly instructs obtaining an API Key from clawjob.upcv.tech and installing an MCP server — a clear mismatch between claimed requirements and the actual instructions.
!
Instruction Scope
The SKILL.md instructs the agent (or user) to: install and use an MCP server (via npx), call many MCP tools, generate PDFs, create a monitor.sh script in the user's home, write reports to ~/.jobsclaw/reports, write ats-records/ files, and schedule cron/launchd jobs. It also embeds a command that runs the 'claude' CLI inside the monitor script. These filesystem writes and scheduled autonomous executions are beyond a purely conversational skill and are not declared in the skill metadata. While they are coherent with 'monitoring' functionality, they materially expand the skill's scope and privileges (files, scheduled execution, local state).
!
Install Mechanism
There is no formal install spec in the registry, but the instructions explicitly tell the user to run: 'claude mcp add upcv -- npx @upcv/mcp-server --api-key YOUR_API_KEY'. That runs a third‑party npm package via npx (dynamic download/execution). This is a moderate risk: code will be fetched from npm at runtime; the skill metadata does not declare or vet this. The skill itself does not include a vetted install artifact; execution relies on remote package installation initiated by the user/agent.
!
Credentials
The manifest lists no required environment variables or primary credential, yet SKILL.md repeatedly instructs obtaining and using an API Key from clawjob.upcv.tech and passing it to the MCP server install command. Additionally, the runtime expects the 'claude' CLI to be available (used in monitor.sh) but 'claude' is not declared as a required binary. This is an incoherence between declared and actual credential/binary needs.
!
Persistence & Privilege
Although always:false, the skill's instructions explicitly create persistent artifacts (monitor.sh, ~/.jobsclaw/reports/, ats-records/) and register them as scheduled tasks via cron or launchd, causing the agent/cli to run periodically. That gives the skill a persistent execution footprint on the host (scheduled invocations of the 'claude' CLI that may call MCP endpoints). The manifest does not state this persistence, so users may not realize the agent will set up recurring jobs and local storage.
What to consider before installing
Before installing or enabling this skill, consider the following: - The SKILL.md requires an API Key from clawjob.upcv.tech, but the skill metadata does not list any required env vars or credentials — ask the publisher to clarify and declare the exact credential(s) needed. - The instructions tell you (or the agent) to run an npx command to fetch @upcv/mcp-server. That downloads and runs code from the npm registry at runtime. Inspect the npm package (source repository and recent releases) before running npx and only use packages from maintainers you trust. - The skill assumes the 'claude' CLI is available and will place a monitor.sh in your home and schedule it via cron/launchd. This creates persistent scheduled jobs that will autonomously invoke the CLI and perform queries. If you enable monitoring, review the generated monitor.sh and the cron/launchd plist before loading them, and consider running the queries manually first. - The skill writes local files (~/.jobsclaw/reports and ats-records/) that may contain extracted personal data (resume fields, job links). Decide whether you are comfortable storing this information locally and inspect the file contents format. - Do not supply highly sensitive fields (ID numbers, government IDs) through automated flows — the SKILL.md itself warns to fill those manually; follow that guidance. - If you proceed, create and use a scoped, revocable API key (if supported), check the privacy policy of clawjob.upcv.tech, and inspect the @upcv/mcp-server package source. Consider running the MCP install and monitor setup in a controlled environment (e.g., an isolated account or VM) first. If you want, I can list the exact lines in SKILL.md that reference the API key, npx install, claude CLI, and the monitor script so you can show them to the publisher or review them in more detail.

Like a lobster shell, security has layers — review code before you run it.

latestvk97esxbzah7mr3ssxfaaxanahh82tjc5

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments