Community라이팅 & 에디팅github.com

abullaisi/upwork-skills

AI agent skills for Upwork freelancers, from a real Top Rated Plus playbook. Free, open, community-written. Not affiliated with Upwork.

upwork-skills란 무엇인가요?

upwork-skills is a Claude Code agent skill that aI agent skills for Upwork freelancers, from a real Top Rated Plus playbook. Free, open, community-written. Not affiliated with Upwork.

지원 대상Claude Code~Codex CLI~Cursor
npx skills add abullaisi/upwork-skills

Installed? Explore more 라이팅 & 에디팅 skills: steipete/notion, affaan-m/seo, affaan-m/brand-voice · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

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.

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.

관련 스킬

steipete/notion

Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.

community

affaan-m/seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.

community

affaan-m/brand-voice

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

community

affaan-m/crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

community

affaan-m/x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

community

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

community