Agent skill

Upwork Job Qualifier

by abullaisi in abullaisi/upwork-skills

Decide whether an Upwork job post is worth applying to before spending Connects.

MITAuto-check passed

Install Upwork Job Qualifier

skills CLI
$ npx skills add abullaisi/upwork-skills --skill upwork-job-qualifier -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install abullaisi/upwork-skills upwork-job-qualifier --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/abullaisi/upwork-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/upwork-job-qualifier .claude/skills/upwork-job-qualifier && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
upwork-job-qualifier
GitHub stars
114
Used in
1 other repo
Token cost
~2.2k tokens
SKILL.md length
1,249 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Decide whether an Upwork job post is worth applying to before spending Connects.

  • Works in 3 steps: The job post, pasted in full. → The "About the client" panel, pasted:… → The user's rate and niche, so the math…
  • The user pastes an Upwork job post (or invitation) and wants a verdict (apply
  • SKILL.md covers Inputs, Instant skips (any one of…, The client-history cross-check… and Soft flags (two or more means…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Upwork Job Qualifier is an agent skill from abullaisi/upwork-skills. Decide whether an Upwork job post is worth applying to before spending Connects. Use when the user pastes an Upwork job post (or invitation) and wants a verdict (apply, skip, or apply with caution). Triggers include "is this job worth it", "should I apply", "check this job post", "is this client legit", "worth my Connects", "red flags in this job". Screens for scams, bad-client patterns, and dressed-up low-tier work, then weighs the Connects economics. Companion to upwork-proposal-writer (after an apply verdict)…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AI agent skills for Upwork freelancers, from a real Top Rated Plus playbook. Free, open, community-written. Not affiliated with Upwork. The licence is MIT.

When your agent uses it

  • The user pastes an Upwork job post (or invitation) and wants a verdict (apply
  • Apply with caution)
  • Include is this job worth it
  • Check this job post

Example prompts

  • “is this job worth it”
  • “should I apply”
  • “check this job post”
  • “/upwork-job-qualifier”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. The job post, pasted in full.
  2. The "About the client" panel, pasted: payment verified or not, total spent, number of hires, average hourly rate paid, hire rate…
  3. The user's rate and niche, so the math below has a reference point.

What it can do on your machine

Read from SKILL.md and the folder at commit dd06254. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • upwork.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Upwork Job Qualifier loads about 2.2k tokens when it runs. Until then it costs about 153 tokens; SKILL.md has 1,249 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from abullaisi/upwork-skills at commit dd06254, republished under its MIT licence (© abullaisi). 1,249 words, ~2,186 tokens.

Download SKILL.mdSave it as .claude/skills/upwork-job-qualifier/SKILL.md (or your agent's skills folder).
name
upwork-job-qualifier
description
Decide whether an Upwork job post is worth applying to before spending Connects. Use when the user pastes an Upwork job post (or invitation) and wants a verdict (apply, skip, or apply with caution). Triggers include "is this job worth it", "should I apply", "check this job post", "is this client legit", "worth my Connects", "red flags in this job". Screens for scams, bad-client patterns, and dressed-up low-tier work, then weighs the Connects economics. Companion to upwork-proposal-writer (after an apply verdict) and upwork-invitation-responder (after a skip verdict on an invitation).

Upwork Job Qualifier

Every proposal costs Connects, and the platform's own AI will never tell a freelancer to keep their money: application volume is the platform's revenue. This skill's whole job is the advice that structurally cannot come from inside: when not to apply. Method extracted from a Top Rated Plus freelancer's real invitation ledger and vetting decisions, plus Upwork's own published scam and client-screening guidance.

Inputs

  1. The job post, pasted in full.
  2. The "About the client" panel, pasted: payment verified or not, total spent, number of hires, average hourly rate paid, hire rate, member-since date, and the category the job is filed under. This panel decides more verdicts than the job text does. If the user didn't paste it, ask for it before ruling.
  3. The user's rate and niche, so the math below has a reference point.

Profile shortcut: if a stored profile file exists (upwork-profile.md in the working directory or ~/.claude/), read rate and niche from it and ask only for what's missing or not stated concretely (a rate line that says "ask me" means ask).

Instant skips (any one of these ends the evaluation)

  • Any request to pay a fee, buy anything, do unpaid test work, or accept payment outside Upwork.
  • Pressure to move communication off-platform before a contract exists.
  • Requests for personal information beyond a normal work discussion.
  • Payment not verified AND no spend history, on a job promising premium rates.
  • A post with no scope, no budget signal, and careless writing throughout. Vague titles with empty descriptions are the fake-post signature.

The client-history cross-check (the highest-value move)

Job titles are marketing. The client's history is data. Run the math:

  • Spend per hire: total spent divided by hires. A "specialist" job from a client averaging under $100 per hire is a low-tier gig wearing a nice title.
  • Average hourly rate paid vs the user's rate. A client who has paid $8/hr across twelve hires will not pay $80/hr for hire thirteen.
  • Category coherence: a premium-sounding title filed under General Virtual Assistance, with data-entry skill tags, is telling the truth in the metadata and lying in the title. Trust the metadata.
  • On invitations: the personalized note carries no signal. Invite notes are often templated. The client's posting history is the signal; the flattery is not.

Worked example (anonymized, from the method author's real ledger): a "$20 Shopify CRO Specialist" invitation looked plausible until the panel showed roughly $48 spend per hire, a $7.59 average hourly rate paid, and a General Virtual Assistance category history. Verdict: data-entry-tier work in a specialist costume. Declined, with a reply, because unanswered invitations are a visible stat.

Soft flags (two or more means apply-with-caution or skip)

  • "I promise you'll get a 5-star review" or any review offered as payment.
  • Price pressure before scope discussion ("can you cut me a deal").
  • "The last freelancer was terrible" used as leverage. That story usually has two sides, and the next chapter stars the user.
  • A chaotic, unstructured brief where requirements arrive as a stream of consciousness.
  • Rushed hiring with no questions asked. Clients who hire in an hour churn just as fast.
  • Job posted more than ~48 hours ago with many proposals already: a weaker use of Connects regardless of quality, since early proposals capture the client's attention.
  • Fixed-price with a large scope and no visible budget number: flag it, that combination is where scope creep lives.

Positive signals

  • Payment verified, real spend history, and an average paid rate within reach of the user's rate.
  • Scope, deliverables, and budget stated plainly. Clients who write clear briefs run clear projects.
  • The client's past jobs live in the same category as this one, at consistent rates.
  • Posted recently, moderate proposal count: the window where a strong proposal actually gets read.

Connects economics (the money math)

  • Connects cost real money (~$0.15 each purchased; a limited free monthly allotment otherwise, more with Freelancer Plus). Every application is a purchase decision.
  • Boosting is an auction: winning bids commonly run 10-20 Connects for a top-4 slot, roughly 17% more likely to be seen, with first place historically converting around twice as often. Boost only strong-fit jobs from verified high-quality clients. Boosting a weak fit is paying extra to lose faster.
  • Decision rule: the worse the client-history math, the lower the acceptable Connects spend. A job that fails the cross-check is worth zero Connects, however good the title feels.
Show full SKILL.md (519 more words)Show less

When the user has no track record yet

The math above assumes a freelancer with a position to protect. Someone with no reviews and no badge is running a different calculation, and pretending otherwise gives them advice built for a situation they are not in. What changes:

  • Winnability enters the verdict, not just worth. A job can pass every client-history check and still be a poor use of Connects for a beginner, because clients who filter on Job Success Score or badge tier will never see the proposal. Weigh that in, and prefer jobs where the client has few or no prior hires: they are less likely to be filtering on credentials that a beginner does not have yet.
  • Scope small on purpose. A first contract that finishes cleanly and earns a genuine review is worth more than a larger one that stalls. Favor tight, well-defined jobs over ambitious ones, for now.
  • Scam screening matters more here, not less. New freelancers are targeted precisely because they are eager and have nothing to lose by taking a risk. Every instant skip above stays absolute at this stage. This is the one part of the method that does not soften for beginners.
  • The rate-gap rule loosens slightly, and only deliberately. A client paying below the user's target rate is normally a skip. At zero reviews it can be a considered tradeoff for the first two or three contracts, if the scope is small and the client history is clean. Name it as a tradeoff with an endpoint, never as a habit.

Honesty note: this method was extracted from an established freelancer's ledger. The beginner adjustments above are reasoned from the same evidence rather than lived at that stage, and the verdict should say so when it leans on them.

Verdict format

No client panel, no verdict. If the About the Client panel wasn't pasted, reply with a HOLD: list what the post alone shows, flag any risks, and request the panel (payment verified, total spent, hires, average rate paid, member since). Never rule APPLY or SKIP on job text alone.

One short paragraph: APPLY / SKIP / APPLY WITH CAUTION, the top two or three reasons in plain language, and the next step. On APPLY, hand off to upwork-proposal-writer. On SKIP for an invitation, hand off to upwork-invitation-responder, because silence is a visible stat and a graceful decline is free. On CAUTION, name exactly what to verify before spending (usually one clarifying question to the client).

Voice rules (hard)

  • Verdict first, reasons second, no hedging paragraphs.
  • No em dashes. Plain words, contractions fine.
  • Never shame the user's pipeline; a thin month makes bad jobs look better, so state the math and let it argue.

Sources and provenance

Method from a Top Rated Plus freelancer's real invitation ledger (40 invitations, 2022-2026) and documented vetting decisions. Official guidance:

This skill is not affiliated with or endorsed by Upwork.

© abullaisi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in upwork-job-qualifier of abullaisi/upwork-skills.

Open the folder on GitHubat commit dd06254

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in abullaisi/upwork-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Upwork Job Qualifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Upwork Job Qualifier compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Upwork Job Qualifier this skillabullaisi/upwork-skills1141 repos~2.2kAutomated safety check: PassMIT
Decidealirezarezvani/claude-skills28k—~871Automated safety check: PassMIT
Technical Job Searchgithub/awesome-copilot40k—~1.2kAutomated safety check: PassMIT
Job Application AssistantMadsLorentzen/ai-job-search45k—~1.2kAutomated safety check: NotesMIT
Job Auto Applysundial-org/awesome-openclaw-skills663—~1.7kAutomated safety check: PassNone
Python Background Jobswshobson/agents40k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Decide

    alirezarezvani/claude-skills

    /cs:decide <memo — Log a decision to two-layer memory via decision-logger.

    28k GitHub stars~871 tokensUpdated 1 mo ago
    Auto-check passed
  • Technical Job Search

    github/awesome-copilot

    Official

    A skill your agent uses when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV/resume, writing a cover letter, evaluating a job offer…

    40k GitHub stars~1.2k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Job Application Assistant

    MadsLorentzen/ai-job-search

    Evaluates job postings against your profile, then tailors a LaTeX CV and cover letter and prepares interview answers for the roles you pursue.

    45k GitHub stars~1.2k tokensUpdated yesterday
    Business, Finance & HRAuto-check: notes
  • Job Auto Apply

    sundial-org/awesome-openclaw-skills

    Automated job search and application system for Clawdbot. An agent skill from sundial-org/awesome-openclaw-skills.

    663 GitHub stars~1.7k tokensUpdated 7 mo ago
    Business, Finance & HRAuto-check passed
  • Python Background Jobs

    wshobson/agents

    Python background job patterns including task queues, workers, and event-driven architecture.

    40k GitHub stars~1.8k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Job Hunt Tracker

    LeoYeAI/openclaw-master-skills

    When user asks to track job applications, manage job search, log interview, applied for job, job application status, track where I applied, job search organizer, application follow up, offer…

    2.2k GitHub stars~4.8k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed

More from abullaisi/upwork-skills

  • Upwork Client Messenger

    abullaisi/upwork-skills

    Draft mid-contract messages to a freelance client on Upwork or similar platforms.

    114 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Upwork Invitation Responder

    abullaisi/upwork-skills

    Respond to an Upwork "Invitation to Interview" fast and well.

    114 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Upwork Profile Optimizer

    abullaisi/upwork-skills

    Audit and improve an Upwork freelancer profile. An agent skill from abullaisi/upwork-skills.

    114 GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • Upwork Proposal Writer

    abullaisi/upwork-skills

    Draft or review an Upwork proposal (cover letter) using the five-move method extracted from a Top Rated Plus freelancer's winning proposals, corrected for the AI era.

    114 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed

Questions about Upwork Job Qualifier

What does Upwork Job Qualifier do?

Decide whether an Upwork job post is worth applying to before spending Connects. Upwork Job Qualifier is an agent skill from abullaisi/upwork-skills. Decide whether an Upwork job post is worth applying to before spending Connects.

When should I use Upwork Job Qualifier?

Upwork Job Qualifier fits situations like: the user pastes an Upwork job post (or invitation) and wants a verdict (apply; apply with caution); include is this job worth it; check this job post.

How do I install Upwork Job Qualifier in Claude Code?

Run `npx skills add abullaisi/upwork-skills --skill upwork-job-qualifier -a claude-code`. Or copy the skill folder (upwork-job-qualifier in abullaisi/upwork-skills) into .claude/skills/upwork-job-qualifier in your project. Claude Code loads it when a task matches its description.

How do I install Upwork Job Qualifier in Codex?

Run `npx skills add abullaisi/upwork-skills --skill upwork-job-qualifier -a codex`. Or copy the skill folder (upwork-job-qualifier in abullaisi/upwork-skills) into .agents/skills/upwork-job-qualifier in your project. Codex loads it when a task matches its description.

Can I use Upwork Job Qualifier in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add abullaisi/upwork-skills --skill upwork-job-qualifier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upwork-job-qualifier, .gemini/skills/upwork-job-qualifier, .github/skills/upwork-job-qualifier and .opencode/skills/upwork-job-qualifier in your project.

What does Upwork Job Qualifier need to run?

SKILL.md names no scripts, command-line tools or credentials: Upwork Job Qualifier is instructions for the agent only.

Does Upwork Job Qualifier access the network?

SKILL.md names 1 domain. As links in the text: upwork.com. This is read from the text; nothing was executed.

Is Upwork Job Qualifier safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Upwork Job Qualifier use?

Upwork Job Qualifier is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Upwork Job Qualifier use?

About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Upwork Job Qualifier?

Skills that share tags, products or a category with Upwork Job Qualifier: Decide (alirezarezvani/claude-skills, 28k stars), Technical Job Search (github/awesome-copilot, 40k stars), Job Application Assistant (MadsLorentzen/ai-job-search, 45k stars) and Job Auto Apply (sundial-org/awesome-openclaw-skills, 663 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Upwork Job Qualifier?

abullaisi (a GitHub user) maintains it in abullaisi/upwork-skills, which has 114 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 5, 2026.

Source: abullaisi/upwork-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.