GLM-V-Resume-Screen
Analysis
This skill matches its resume-screening purpose, but it uses a Zhipu API key and sends resume contents to Zhipu's model, so candidate data and credentials should be handled carefully.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`PyMuPDF` is required (`pip install PyMuPDF`).
The local PDF workflow depends on a manually installed Python package. The dependency is disclosed and purpose-aligned, but package installation changes the local environment.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
This script reads the key from the `ZHIPU_API_KEY` environment variable
The skill requires a provider API credential. This is expected for the stated Zhipu integration, but the key can authorize account usage and billing.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Local PDF files are converted page-by-page into images (base64) before sending to the model.
Resume contents, including local PDF pages, are transmitted to an external model provider. This is disclosed and central to the skill, but it involves sensitive candidate data crossing a provider boundary.
