Job Auto Apply
SuspiciousAudited by ClawScan on May 10, 2026.
Overview
The skill is openly about auto-applying to jobs, but it documents high-impact account automation, optional unreviewed submissions, CAPTCHA/proxy bypass, and broad credential/session use that should be reviewed carefully.
Only install this if you are comfortable with an agent handling job-platform accounts and personal application data. Keep dry-run and manual confirmation on, avoid CAPTCHA/proxy bypass, use least-privilege credentials, review every cover letter and screening answer, and protect or delete stored profile and application-log files.
Findings (4)
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.
It could send unintended, inaccurate, or career-impacting applications under the user's name.
The skill allows real job applications and employer screening answers to be submitted without making per-application human approval mandatory.
submits applications automatically or with user confirmation ... Submit applications (with confirmation if enabled) ... Screening questions (using AI when needed)
Keep dry-run and manual confirmation enabled, review every application package and screening answer, and set strict per-run limits.
This can violate job-platform terms, trigger account locks, or cause applications to be associated with suspicious automation.
The integration guidance explicitly recommends CAPTCHA-solving services and residential proxies, which can bypass platform anti-bot controls.
Captcha Handling - Use 2Captcha or Anti-Captcha services ... Captcha Blocks: Reduce frequency, use residential proxies
Prefer official APIs and manual checkpoints; avoid CAPTCHA-bypass services, proxy evasion, or scraping flows that a platform disallows.
A token or persisted session could grant more access to the user's job-platform account than expected.
The documented LinkedIn OAuth scope includes social write authority, and the workflow contemplates persistent authenticated sessions, which is broader account access than clearly needed for job applications.
Required Scopes: `r_basicprofile`, `r_emailaddress`, `w_member_social` ... Maintain authenticated sessions ... Handle cookie persistence ... Refresh tokens before expiration
Use least-privilege OAuth scopes, declare required credentials clearly, avoid social-write permissions unless strictly necessary, and provide token revocation and session cleanup steps.
If the profile or logs are stale, exposed, or edited incorrectly, the agent could reuse sensitive or inaccurate information in future applications.
The skill relies on a saved profile containing sensitive personal, career, document, and screening-answer data for reuse across applications.
"full_name", "email", "phone", "location" ... "resume_path": "~/Documents/resume.pdf" ... "screening_answers"
Store the profile locally with restricted permissions, review it before each run, avoid unnecessary sensitive fields, and periodically delete old application logs.