AI Upwork Proposal Writing & Job Tracking System

v1.0.3

AI-assisted tool that filters Upwork jobs, drafts personalized proposals, tracks applications locally, and learns from outcomes for continuous improvement.

0· 82·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the implementation: scripts and instructions focus on filtering job text, drafting proposals, scoring, and appending local logs and vault entries. There are no unrelated requirements (no cloud credentials, no external binaries).
Instruction Scope
SKILL.md and the included script restrict reads/writes to files inside the upwork-auto-apply/ folder and require the user to paste job data; pre-apply-check.sh is read-only and only checks .upwork/APPLICATION_LOG.md. This is coherent, but the skill will store full proposal drafts and job details (personal data) in APPLICATION_LOG.md and may append to PROPOSAL_VAULT.md — users should treat those files as sensitive.
Install Mechanism
No install spec and no external downloads. The only code is a small shell script (pre-apply-check.sh) which is local and uses standard Unix utilities (bash, awk, grep). This is low-risk and proportional to the stated purpose.
Credentials
The skill requests no environment variables, no credentials, and no privileged config paths. The only personal data used is what the user enters into FREELANCER_PROFILE.md (e.g., Upwork profile link, rates, proof points), which is expected and justified by the functionality.
Persistence & Privilege
always:false (default) and no code seeks permanent or cross-skill configuration. The skill expects to write to its own local log and vault files (normal for a tracker). Autonomous model invocation is enabled by platform default but not combined with any other concerning privileges here.
Assessment
This skill appears to do what it says and runs locally, but take these common-sense precautions before installing or using it: - Do not put the upwork-auto-apply/ folder (especially .upwork/APPLICATION_LOG.md and FREELANCER_PROFILE.md) into public version control; those files contain personal data and proposal drafts. - Verify you run any included scripts from the upwork-auto-apply/ root as intended, because the shell script uses relative paths; running it from a different directory could change which files are accessed. - Review and edit every drafted proposal before submitting on Upwork (the tool is intentionally designed for manual submission). - If you ever see a future version that adds network calls, environment variables, or an install step that downloads code, treat that as higher risk and re-review before use. - Keep backups (and consider file permissions) for APPLICATION_LOG.md if you rely on it for history. Overall: the skill is coherent and low-risk for local use, provided you safeguard the files that contain your personal information.

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

auto-bidvk973g2dxjyfnzwcbv6p4bm3ay983ex2zfreelance-growthvk973g2dxjyfnzwcbv6p4bm3ay983ex2zlatestvk973g2dxjyfnzwcbv6p4bm3ay983ex2zlead-genvk973g2dxjyfnzwcbv6p4bm3ay983ex2zrevenue-aivk973g2dxjyfnzwcbv6p4bm3ay983ex2zupwork-automationvk973g2dxjyfnzwcbv6p4bm3ay983ex2z

License

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

Comments