v1.0.0

HireEase Skill

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 8:24 AM.

Analysis

The skill’s resume/application workflow is mostly purpose-aligned, but it uses powerful HireEase credentials and Google Drive sharing in ways that need careful review before installation.

GuidanceInstall only if you trust the HireEase endpoint and understand that the skill may use stored HireEase credentials, access client records, create real application records, and potentially publish a resume PDF through Google Drive. Do not enter arbitrary base URLs, and prefer manually reviewing the PDF and Drive link before approving submission.

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.

Abnormal behavior control

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.

Tool Misuse and Exploitation

SeverityMediumConfidenceHighStatusNote

SKILL.md

Should you **record the application in HireEase for real**? (`Yes` / `No`) ... `POST {BASE}/api/applications` ... `PATCH {BASE}/api/applications/:id` to set `resumeUrl`

The skill can create and modify HireEase application records. This is aligned with the stated purpose and includes a Yes/No confirmation prompt, but it is still a real account/data mutation.

User impactApproving the workflow can create or update a real application record in HireEase.

RecommendationReview the selected client, job, company, resume link, and application fields before answering Yes to real submission.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityHighConfidenceHighStatusConcern

SKILL.md

2. `base url` to use? ... `HIREEASE_AGENT_EMAIL` ... `HIREEASE_AGENT_PASSWORD` ... `POST {BASE}/api/auth/login` with `{ "email", "password" }`

The instructions combine a user-provided base URL with sending HireEase agent credentials to `{BASE}/api/auth/login`. The visible artifact shows no allowlist or other boundary to ensure those credentials are only sent to trusted HireEase hosts.

User impactIf the wrong or a malicious base URL is supplied, the agent could send HireEase login credentials to an unintended server, and the resulting token could be used for private client and application operations.

RecommendationUse only a preconfigured, allowlisted HireEase base URL; declare the required credentials in metadata; use least-privilege tokens; and require explicit confirmation before credentialed actions.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityMediumConfidenceHighStatusConcern

SKILL.md

If `No`: only proceed with browser automation if it’s available AND I’m already logged into the client Google account/session. ... Attempt to upload the generated PDF to Google Drive under the client’s session. Copy the “Anyone with the link” public Viewer URL.

The workflow may use an existing Google account browser session and change Drive sharing to an anyone-with-link public viewer URL. That crosses an account/data boundary and makes the generated resume publicly link-accessible.

User impactA resume PDF could be uploaded through a logged-in Google account and made accessible to anyone who receives the link.

RecommendationPrefer having the user manually provide the Drive link, or require a clear final approval before using a browser session, uploading to Drive, and enabling public link sharing; use a dedicated folder/account where possible.